CX-10

DeliveryReceipt

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
receiptId	string	required	—
recordRefs	array	required	—
boundary	string	required	source_acquired · local_durable · canonical_admitted · published · consumer_accepted
outcome	string	required	accepted · rejected · quarantined · duplicate · filtered · pending · expired
recordedAt	string	required	—
authorityRef	string	required	—
reasonCode	any	required	—
evidenceRefs	array	required	—
isSynthetic	boolean	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "receiptId": "receipt-fixture-01",
  "recordRefs": [
    "record-fixture-01"
  ],
  "boundary": "local_durable",
  "outcome": "accepted",
  "recordedAt": "2026-09-22T12:00:00Z",
  "authorityRef": "fixture:simulator",
  "reasonCode": null,
  "evidenceRefs": [],
  "isSynthetic": true
}