CX-10

AsyncOperation

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
operationId	string	required	—
kind	string	required	—
state	string	required	queued · running · succeeded · failed · cancelled
progress	number	required	—
resultRef	any	required	—
errorRef	any	required	—
idempotencyKey	string	required	—
submittedAt	string	required	—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "operationId": "operation-fixture",
  "kind": "discover",
  "state": "queued",
  "progress": 0,
  "resultRef": null,
  "errorRef": null,
  "idempotencyKey": "fixture-request-01",
  "submittedAt": "2026-09-22T12:00:00Z"
}