CX-10

RecoveryPlan

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
recoveryId	string	required	—
planId	string	required	—
operation	string	required	replay · backfill · reprocess
range	object	required	—
inputEvidenceRefs	array	required	—
mappingVersion	string	required	—
targetPublicationRef	string	required	—
sideEffectPolicy	any	required	—
previewDigest	string	required	—
approvalRef	any	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "recoveryId": "recovery-fixture",
  "planId": "plan-fixture-01",
  "operation": "reprocess",
  "range": {
    "from": "2026-09-22T12:00:00Z",
    "to": "2026-09-22T13:00:00Z"
  },
  "inputEvidenceRefs": [
    "evidence:fixture-01"
  ],
  "mappingVersion": "2",
  "targetPublicationRef": "fixture:isolated-output",
  "sideEffectPolicy": "suppress_operational_actions",
  "previewDigest": "cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
  "approvalRef": null
}