CX-10

ConnectorManifest

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
connectorId	string	required	—
packageVersion	string	required	—
configSchemaRef	string	required	—
sourceContractRefs	array	required	—
capabilities	array	required	items → Capability
runtimePlacements	array	required	—
sbomRef	any	required	—
signatureRef	any	required	—
implementationStatus	string	required	unassessed · not_built · built · tested
qualificationStatus	string	required	not_run · failed · qualified

References these contracts

Capability

Depended on by

No other contract depends on this one.

Synthetic example

{
  "connectorId": "CS-CON-0001",
  "packageVersion": "0.3.0",
  "configSchemaRef": "urn:optimon:coresync:0.3:config:CS-CON-0001",
  "sourceContractRefs": [
    "SC-CS-CON-0001"
  ],
  "capabilities": [
    {
      "name": "sourceWrite",
      "availability": "unsupported",
      "condition": null,
      "evidenceRefs": []
    }
  ],
  "runtimePlacements": [
    "plant"
  ],
  "sbomRef": null,
  "signatureRef": null,
  "implementationStatus": "not_built",
  "qualificationStatus": "not_run"
}