Skip to main content
Assurance work is coordinated through workpapers, exports, inboxes, and status pings. The documents hold evidence, but the operational truth lives somewhere else. States remain opaque: what is official, who can act, what is blocked, and what has been released. Soteris makes that operational layer explicit. An engagement, not a file, is the unit of record. Every engagement has a lifecycle state, controlled inputs, a review authority boundary, released records, and receipts that let a permitted party confirm what was released. Agents prepare the work, humans conclude, and the engine remains the system of record throughout.
v0 of Soteris documentation describes the states, record shapes, actor boundaries, and verification checks a partner system or agent should reason with today. The docs are not an API reference. Programmatic surfaces expand later, and each page states what is live now versus contract preview.

Start

What Soteris is, surface exposure, and disclosure boundaries

Workflow

The engagement lifecycle, who can act, and where it stops

Records

The five shapes a partner or agent reads: inputs, artifacts, releases, receipts, status

Verification

What a receipt proves, and what stays private

Examples

Synthetic records and a worked agent read path, showing each shape without a live endpoint.

Reference

Canonical states, fields, schemas, and error categories

​
What Soteris provides

​
How the system fits together

  1. Portal: The system of record for engagement state, inputs, artifacts, and releases.
  2. Backend control boundary: Validates transitions, records events, stores references.
  3. Agent runtime: The private layer that prepares drafts, findings, and classifications.
  4. Review and release: Where Soteris controls approval and release authorization.
  5. Verification: The inspection layer for released records and receipts.
The layers above the portal are described here only at the boundaries. How the agent runtime works, and how review decides, are not part of this contract.

​
Reading order

These docs answer “how do I interoperate with Soteris,” not “how does Soteris reach its judgment.” State names, record shapes, and receipts are published. Gate criteria, review reasoning, scoring, prompts, and client data are not, at any access tier. The full rule is the Disclosure boundary.