Evidence Chain
- Claim or handle
- Operational substrate
- Behavioral or deterministic test
- Raw evidence
- Interpretation and non-claims
- Canonical manifest
- Tamper-evident receipt
- Append-only maintenance
- External verification, if earned
Layer Translation
- For technical readers: closest to a transparency-log and reproducible-build mindset, but applied to machine-mediated evidence claims rather than only software artifacts.
- For institutional and legal readers: closest to an audit dossier that records what was tested, what passed, what failed, what was out of scope, and what evidence package supports the result.
- For operators and procurement readers: a way to inspect the substrate behind a claim instead of relying on a presentation, dashboard, or assertion.
What Sovrient Is Like
Sovrient combines several familiar evidence patterns into one system. It is not identical to any of them, but each helps explain one part of the architecture.
| Familiar pattern | What it helps explain | Where the analogy stops |
|---|---|---|
| Software provenance systems such as Sigstore Rekor and in-toto | Signed artifacts, transparency logs, attestations, and replayable build or evidence chains. | Sovrient is not only about software packages or supply-chain metadata; it applies evidence discipline to machine-mediated claims and real-world event surfaces. |
| Certificate Transparency and timestamping systems such as OpenTimestamps | Append-only public records, existence proofs, and tamper-evident logs. | A timestamp or log entry proves a record existed; it does not prove the underlying claim is true. |
| Reproducible scientific or data pipelines | Declared inputs, deterministic reruns, and inspectable outputs. | Sovrient adds admissibility boundaries, non-claims, and maintained evidence state. |
| Incident-review or audit-dossier practices | Clear separation between in-scope evidence, out-of-scope material, findings, and limits. | Sovrient is not a court, regulator, or formal legal admissibility doctrine. |
| Public status and machine-readable state surfaces | Live JSON, status pages, public evidence endpoints, and inspectable system state. | Sovrient is not asking readers to trust a dashboard alone; it exposes the underlying protocol and evidence chain. |
External names are reference points only. Sovrient is independent from and unaffiliated with these projects or organizations unless explicitly stated.
What Sovrient Is Not
- Not a court or legal admissibility doctrine.
- Not a compliance certification service.
- Not a model-safety certification.
- Not a parametric insurance oracle.
- Not a claim that a timestamp proves truth.
- Not a claim that a hash proves meaning.
- Not a substitute for independent audit, provider attestation, or expert review.
- Not a promise that every model or lane will reproduce every result.
What A Receipt Proves
A receipt can help show that a manifest-bound evidence package existed in a specific state and that post-seal modification is detectable from the moment of sealing onward.
What A Receipt Does Not Prove
A receipt does not prove the underlying claim is true, does not replace independent audit, does not certify model safety, and does not prove model intent. External verification is added only when reproduction, audit, provider attestation, or hardware attestation actually exists.