CX-10

ReleasePackage

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
releaseId	string	required	—
scope	ref → Scope	required	—
manifestRef	string	required	—
configurationDigest	string	required	—
sourceContractRefs	array	required	—
mappingRefs	array	required	—
approvalRef	string	required	—
signatureRef	string	required	—
rollbackReleaseRef	any	required	—

References these contracts

Scope

Depended on by

No other contract depends on this one.

Synthetic example

{
  "releaseId": "release-fixture",
  "scope": {
    "tenantId": "fixture-tenant-a",
    "siteId": "fixture-plant-01",
    "environment": "test"
  },
  "manifestRef": "manifest:fixture",
  "configurationDigest": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "sourceContractRefs": [
    "source-contract-fixture"
  ],
  "mappingRefs": [
    "mapping-fixture-01"
  ],
  "approvalRef": "approval:fixture",
  "signatureRef": "signature:fixture-not-cryptographic",
  "rollbackReleaseRef": null
}