CX-10

QuarantineCase

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
caseId	string	required	—
scope	ref → Scope	required	—
recordRefs	array	required	—
failureClass	string	required	structural · semantic · identity · permission · delivery · evidence · provider
reasonCode	string	required	—
state	string	required	open · assigned · remediated · reprocessed · closed
ownerRef	any	required	—
originalEvidenceRefs	array	required	—
resolutionRef	any	required	—

References these contracts

Scope

Depended on by

No other contract depends on this one.

Synthetic example

{
  "caseId": "case-fixture",
  "scope": {
    "tenantId": "fixture-tenant-a",
    "siteId": "fixture-plant-01",
    "environment": "test"
  },
  "recordRefs": [
    "record-fixture-01"
  ],
  "failureClass": "semantic",
  "reasonCode": "UNIT_INCOMPATIBLE",
  "state": "open",
  "ownerRef": null,
  "originalEvidenceRefs": [
    "evidence:fixture-01"
  ],
  "resolutionRef": null
}