Verify it yourself

Most products in this space ask to be believed. This one can be checked, and the check is the demonstration.

What verification actually does

1. Re-hashes every file in the bundle and compares against the manifest.
2. Checks the manifest digest against the ledger entry for that run.
3. Checks the entry's prev_entry_hash links to the entry before it, all the way back.
4. Checks the signature over the statement.
5. Replays the recorded decision against the recorded policy and confirms it reaches the same result.

And what it does not

It proves nothing has been altered since the decision was made. It does not prove the decision was right — that is a question about the policy, which is why the policy is versioned, reviewed and identified by commit in every bundle.

A hash chain also proves internal consistency rather than authenticity: somebody who can rewrite the whole evidence branch and re-sign it produces a history that verifies perfectly cleanly. That is why the head is anchored somewhere its owner cannot rewrite, and why the documentation says so first.

Try it on a bundle from the demo

The demo estate's bundles, its public key, and a deliberately tampered copy are published by #95. Until that lands, the demo console carries the same evidence: every run links to its bundle, and each is marked verified by the ingester, which re-ran the checks above rather than taking the bundle's word for it.

Open the demo →