Record schemas - Soteris Developer Docs

Five public record families appear across these docs. Each family is hand-curated for interoperability, not generated from backend schemas, and no page here publishes a raw table or internal event payload.

Families

Record	Purpose	Contract page
`InputRecord`	Describes submitted material and mapping context.	Input records
`ArtifactRecord`	Describes produced work and its review and release status.	Artifact records
`ReleaseRecord`	Describes what was authorized and made available.	Release records
`VerificationReceipt`	Describes what can be inspected about a released record.	Verification receipts
`StatusCard`	Summarizes lifecycle state, owner, blockers, and next action.	Status card

Record flow

How the five record families connect, from input record to verification receipt.

Schema posture

The public schema stays stable so partners can map against it. The implementation underneath is free to change. Field names describe state, shape, and authority; fields that would carry reviewer reasoning, scoring, or gate output are excluded at design time, per the Disclosure boundary.

These docs do not publish raw tables, internal event payloads, prompt inputs, scoring outputs, procedure programs, or review rationale.