Skip to main content
These docs are a contract, not a cookbook. The contract defines how to interoperate with Soteris: the states, the record shapes, who can act, and what a receipt proves.
Nothing here states how the work is judged. The interface is public. The judgment is not.
This boundary is content discipline, not access control. Every page is written on the assumption that it will be forwarded and pasted into another system’s context window.

​
Published and never published

​
The page test

Every page passes three lines before it ships:
  1. Interface, not judgment. It describes the surface an actor touches, never how Soteris concludes.
  2. State, not criteria. It names a state and its signal, never the rule that admits or blocks it.
  3. Verify-side, not issue-side. It explains how to confirm what was released, never how it was produced.
A sentence that fails any line does not ship. The operational version of this test is the Exposure checklist.

​
The stable surface

The published vocabulary is the interoperability surface: states, shapes, and receipts. Those are what a partner mapping should build against. The judgment layer sits on the other side of the boundary and is not part of any published surface.