Tenant-scoped system of record
Every governed record is isolated per tenant in PostgreSQL with row-level security, and the API derives the tenant from the credential rather than from a parameter.
Product proof
Sentience is an operating system of record with a governed spine, so the honest version of this page names the boundary as clearly as the capability.
Every governed record is isolated per tenant in PostgreSQL with row-level security, and the API derives the tenant from the credential rather than from a parameter.
A source is stored as its retrieved bytes with a hashed version, so a change is a difference between two retained versions instead of an assertion.
An applicability determination carries the rule version, the inputs, the citation and the time it was made.
Authorization by policy and approval by a person are distinct records, and the console reports them separately.
Events are hashed over their predecessor, so a record altered after the fact fails verification rather than quietly replacing the truth.
Missing authority, missing standing or missing evidence produces a refusal with its reason, never an inferred certainty.
Filing payloads are prepared, validated and bound to an approval today. Transmission stays behind the authority gate until the legal standing for a jurisdiction is recorded.
An acceptance is a receipt from outside the system, so it is only ever shown once such a receipt exists.
Jurisdictional coverage
Verified coverage is measured, never asserted.
The product reports its own coverage rung from verified rules. A jurisdiction counts once a rule has been verified against a cited source version — not once a source has been read. This page shows no coverage figure, because none is asserted here.
See what changes when regulatory change, operational context, human authority, governed action and evidence become one continuous system.
Regulatory change → governed action → proof.