Audit & evidence
The chain
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 that follows it.
The independent verifier
The verifier is decoupled from the writer and uses only the standard library, so verification does not require trusting the code that produced the records. It ships with a 1,000-record fixture.
Exportable windows
An exported window carries its own prevHash and hash, so a third party can recompute the chain over that slice without access to your database.
The anchor is declared, not verified
The window’s 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. The export reports
anchorVerified accordingly rather than implying more than it establishes.
Completeness
Failure outcomes — timeouts, backend errors, internal errors, cost caps, and ok:false responses — are written to the chain as well as successes. The chain evidences what the system did, not only what worked.