Skip to main content
Limited design-partner access Status: Limited design-partner access. The backend contracts in the first table are implemented and replay-tested. They do not yet form a supported operator product.

Contract map

Event-sourced state

An event is an attributable fact about what was requested and accepted. Reducers fold those facts into current state. Replay tests compare rebuilt state with live derived records so a write that bypasses the log or a reducer that drifts becomes visible. Authorization happens before the governed event is appended. Both an allowed operation and a denial remain explainable: the Decision records the policy result, while the Ledger connects an accepted event to the acting principal and decision.

Version and content identity

A checkpoint turns a bounded event range into a stable position. A commit names that checkpointed history. Its commitId identifies the commit object; its contentRoot identifies the covered content. They are not interchangeable. Those guarantees now apply to the combined content root: asset, instruction, label, project-metadata, review, and workflow roots plus the bound taxonomy version. Review state is deliberately outside the content hash, so a review verdict binds a specific annotation hash without moving it. Branches are zero-copy references to history. Merge compares a base, the current branch, and the proposed branch. Non-overlapping changes can merge automatically; typed conflicts remain explicit and can require an authorized adjudication decision.

Routing, review, and machine work

The Router evaluates eligibility and ordering rules for annotation, review, consensus, gold checks, and adjudication. Review outcomes and the decision that follows remain separate records. A machine Job carries its model family, inputs, execution mode, and provenance. The implemented prelabel contract can refuse work before inference when calibration cannot satisfy the declared risk bound. Successful output currently comes from a labeled deterministic stub; real model inference is planned.

Planned target contracts

The following concepts are planned — not available yet:

Common mistakes and limits

  • Replay-proven backend behavior does not imply a shipped screen or end-to-end operator journey.
  • The content root identifies committed content; it is not yet a complete volumetric dataset identity across releases.
  • A Task is not a machine Job.
  • A refusal is a valid terminal result, not a silent failure or automatic fallback.
  • An export is not automatically a Dataset Release.

Next step

Read Public HTTP API for the current transport surface or Dataset release for the planned evidence lifecycle.
OutcomeDistinguish implemented backend contracts from planned operator surfaces and dataset-release behavior.
AvailabilityLimited design-partner access
AudienceML engineers, Data engineers, Data scientists, Technical leaders, AI agents
PrerequisitesRead Version model; Read Roles and provenance
Last verified2026-08-23