CX-10

CommandPermitReference

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
permitRef	string	required	—
issuerAuthorityRef	string	required	—
targetRef	string	required	—
payloadDigest	string	required	—
expiresAt	string	required	—
preconditionEvidenceRefs	array	required	—
ingestionRoleMayIssue	any	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "permitRef": "authority-permit:fixture-only",
  "issuerAuthorityRef": "plane8:fixture",
  "targetRef": "fixture:nonexecuting-target",
  "payloadDigest": "dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd",
  "expiresAt": "2026-09-22T12:01:00Z",
  "preconditionEvidenceRefs": [
    "evidence:fixture-precondition"
  ],
  "ingestionRoleMayIssue": false
}