OptimonCoreSync Studio
IE
CX-10

Checkpoint

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

FieldTypeRequiredPermitted values / reference
checkpointIdstringrequired—
planIdstringrequired—
sourceEpochstringrequired—
partitionstringrequired—
kindstringrequiredwatermark · opaque_token · lsn · offset · sequence · file_version
positionstringrequired—
acceptedThroughRefstringrequired—
recordVersionintegerrequired—
recordedAtstringrequired—

References these contracts

No outbound contract references.

Depended on by

No other contract depends on this one.

Synthetic example

{
  "checkpointId": "checkpoint-fixture",
  "planId": "plan-fixture-01",
  "sourceEpoch": "epoch-01",
  "partition": "0",
  "kind": "sequence",
  "position": "10",
  "acceptedThroughRef": "receipt-fixture-10",
  "recordVersion": 1,
  "recordedAt": "2026-09-22T12:00:00Z"
}