CX-10

ConnectionInstance

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
connectionId	string	required	—
connectorId	string	required	—
scope	ref → Scope	required	—
mode	string	required	simulation · live
configurationRef	string	required	—
configurationDigest	string	required	—
recordVersion	integer	required	—
credentialBindingRef	string	required	—
state	string	required	draft · validated · approved · active · paused · failed · retired
providerVersion	string	required	—
qualificationRef	any	required	—

References these contracts

Scope

Depended on by

No other contract depends on this one.

Synthetic example

{
  "connectionId": "conn-fixture-01",
  "connectorId": "CS-CON-0001",
  "scope": {
    "tenantId": "fixture-tenant-a",
    "siteId": "fixture-plant-01",
    "environment": "test"
  },
  "mode": "simulation",
  "configurationRef": "fixture:cfg-01",
  "configurationDigest": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "recordVersion": 1,
  "credentialBindingRef": "secret-binding:fixture-only",
  "state": "draft",
  "providerVersion": "SIM-UNQUALIFIED",
  "qualificationRef": null
}