CX-10

ContractValidationRequest

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
schemaRef	string	required	—
document	object	required	—
validationMode	string	required	structural · structural_and_semantic
bindingContextRef	any	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "schemaRef": "urn:optimon:coresync:0.3:MeasurementObserved",
  "document": {
    "kind": "MeasurementObserved",
    "subjectRef": "fixture:asset-01",
    "parameterRef": "fixture:temperature",
    "value": 812.5,
    "quantityKind": "temperature",
    "unit": "Cel",
    "uncertainty": 0.5,
    "quality": "good"
  },
  "validationMode": "structural",
  "bindingContextRef": null
}