CX-10

MappingDefinition

40 typed shared schemas, source/config schemas, examples, required fields, old/new compatibility, dependent flows and approval validity.

Acceptance · Changing meaning, required fields or approved mappings invalidates affected approval/test evidence as policy requires. Operations listSourceContracts, validateContract

Synthetic connector workspace. Every profile here is a proposed target. Nothing on this screen is a live, qualified or certified adapter, no payload is a captured vendor wire message, and the simulation engine has no code path to a real endpoint.

bundle status: proposed; not signed V9 canonical schemas← all schemas

Fields

Field	Type	Required	Permitted values / reference
mappingId	string	required	—
version	string	required	—
sourceContractRef	string	required	—
targetContractRef	string	required	—
subjectBindingRef	string	required	—
referenceSetVersions	array	required	—
operations	array	required	—
approvalRef	any	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "mappingId": "mapping-fixture-01",
  "version": "1",
  "sourceContractRef": "source-contract-fixture",
  "targetContractRef": "urn:optimon:coresync:0.3:MeasurementObserved",
  "subjectBindingRef": "fixture:binding-01",
  "referenceSetVersions": [
    "fixture:units-v1"
  ],
  "operations": [
    {
      "operation": "copy",
      "sourcePath": "/value",
      "targetPath": "/data/value",
      "parameters": {}
    }
  ],
  "approvalRef": null
}