Read this first — what "all checks passed" means
A receipt whose checks all pass does not mean the decision was right. It means the record of the decision is intact: the bytes are what was sealed, the signatures verify, and the completeness status is exactly as stated. Whether the decision was correct, fair, or lawful is a question about the world — a receipt proves the record, never the world.
Level 1 — read the receipt page
Every hosted receipt page lists each check it performed in scoped language — "stored hashes recomputed and consistent", "manifest signature valid (Ed25519 ∧ ML-DSA-65)" — and states what the record attests and what it does NOT attest, on every page, at every tier. The page carries no scripts, no third-party calls, and no tracking.
Level 2 — check the address yourself (one shell command)
curl -s https://api.avenic.ai/r/sha384/<digest>/bundle -o bundle.json sha384sum bundle.json # equals the <digest> in the address
The address of a receipt IS the SHA-384 of its bundle bytes.
If anyone — including us — served different bytes under that address, this one command
exposes it. No account, no tooling beyond sha384sum.
Level 3 — re-derive every check from the bytes
The bundle is self-describing JSON: it carries the records, the hash chain, the signatures, and the public-key registry needed to check them — everything re-derives from the bundle bytes alone, with no call to avenic and no secret. The cryptography is standard and documented: SHA-384 hash chains and Merkle roots, hybrid Ed25519 ∧ ML-DSA-65 signatures where both families must verify.
Keep your own copy of bundle.json. A receipt you hold verifies
offline regardless of what happens to the link, the host, or this company.
If a check fails
A receipt page never blurs failure classes: bytes that do not match what was signed render as an integrity failure; input that is not readable as a bundle renders as exactly that — a malformed input, not a tamper finding.