CX-10

AcquisitionPlan

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
planId	string	required	—
connectionId	string	required	—
sourceContractRef	string	required	—
mappingRef	string	required	—
mode	string	required	snapshot · poll · subscribe · history · cdc · file_intake
resourceIds	array	required	—
checkpointRef	any	required	—
budget	object	required	—
overflowPolicy	string	required	pause · reject_with_receipt · approved_shed_with_evidence
publicationRef	string	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "planId": "plan-fixture-01",
  "connectionId": "conn-fixture-01",
  "sourceContractRef": "source-contract-fixture",
  "mappingRef": "mapping-fixture-01",
  "mode": "subscribe",
  "resourceIds": [
    "resource-fixture-01"
  ],
  "checkpointRef": null,
  "budget": {
    "maxRequestsPerSecond": 1,
    "maxInFlight": 1,
    "maxBufferBytes": 104857600
  },
  "overflowPolicy": "pause",
  "publicationRef": "publication-fixture"
}