CX-10

PublicationSubscription

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
subscriptionId	string	required	—
scope	ref → Scope	required	—
publicationRef	string	required	—
contractRef	string	required	—
consumerIdentityRef	string	required	—
filterRef	any	required	—
checkpointRef	any	required	—
permittedTruthContexts	array	required	actual · normative · planned · predicted · scenario · desired
allowSynthetic	boolean	required	—

References these contracts

Scope

Depended on by

No other contract depends on this one.

Synthetic example

{
  "subscriptionId": "sub-fixture",
  "scope": {
    "tenantId": "fixture-tenant-a",
    "siteId": "fixture-plant-01",
    "environment": "test"
  },
  "publicationRef": "pub-fixture",
  "contractRef": "urn:optimon:coresync:0.3:CanonicalEvent",
  "consumerIdentityRef": "identity:fixture-consumer",
  "filterRef": null,
  "checkpointRef": null,
  "permittedTruthContexts": [
    "actual"
  ],
  "allowSynthetic": true
}