Platform
Audit & evidence
Evidence is the point of the whole system. If the record cannot be independently checked, it is a log, not evidence.
How the chain works
Each record’s hash is computed over the record’s canonical serialisation plus the previous record’s hash. Altering any earlier record breaks every hash after it.
- An independent verifier recomputes the chain using only the standard library, so verification does not require trusting the writer’s code.
- Exportable windows carry their own
prevHashandhash, so a third party can verify a slice without access to your database. - Failure outcomes are recorded — timeouts, backend errors, cost caps. The chain evidences completeness, not just success.
What the anchor does and does not prove
An exported window’s anchor is declared, not verified. The first record points outside the window, so it can only be proven to be a chain root when its hash matches the genesis value. Full-chain verification is the stronger check, and it needs the whole chain. We state this rather than letting “exportable and verifiable” imply more than it does.
Where it runs
Decisions, context access and escalations are written through the audit module. A decision chain with a depth metric accompanies the record, so you can see how a conclusion was reached, not only what it was.