Concepts
A mini-encyclopedia of the EvidenceOS primitives. Short, visual, and audit-first.
How we're different
- Evidence system of record, not a case tracker.
- Immutable timeline and explicit approvals with no silent overrides.
- Examiner-ready binders with linked artifacts and tamper-evident logs.
Control
A control is the defined obligation. EvidenceOS stores the definition and versions it.
Run
A run is one execution of a control over a period, with status, evidence, exceptions, and approvals.
Evidence
Evidence is an artifact with hashes, provenance, retention metadata, and a link to a run.
Approval
Approvals are explicit decisions with rationale — no silent overrides.
Binder
Binders export the complete record: evidence index, approvals, exceptions, and ledger excerpt.
Immutable ledger
Every action is appended to a hash-chained audit log you can verify.
No silent overrides
Every override is captured with who/what/why — auditors can replay it.
Policy gates
Sensitive actions require a human gate; automation executes inside rails.
Model independence
LLMs are optional. The system still works deterministically.
Evidence hashing
Artifacts are hashed on upload so exports can prove integrity.
Tamper evidence
Hash chaining makes audit trails tamper-evident without complex infra.
How to read this
Each concept links back to a concrete feature: controls, runs, evidence, approvals, binders, and the ledger.