CX-10

DiscoveryResult

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
discoveryId	string	required	—
connectionId	string	required	—
items	array	required	items → DiscoveredResource
nextPageToken	any	required	—
complete	boolean	required	—
warnings	array	required	—

References these contracts

DiscoveredResource

Depended on by

No other contract depends on this one.

Synthetic example

{
  "discoveryId": "discovery-fixture",
  "connectionId": "conn-fixture-01",
  "items": [
    {
      "resourceId": "resource-fixture-01",
      "sourcePath": "nsu=urn:fixture;s=TempPV",
      "displayName": "Fixture temperature",
      "kind": "tag",
      "schemaRef": "fixture:source-schema-01",
      "sourceUnit": "Cel",
      "nativeCapabilities": [
        "read"
      ],
      "isSynthetic": true
    }
  ],
  "nextPageToken": null,
  "complete": true,
  "warnings": []
}