Evidence package verification

What this page proves — and its honest limits. Every check above runs locally in your browser from data embedded in this file; nothing is sent anywhere. The checks prove the billed records match the signed capture-time audit events, that those events are committed into Merkle block roots, and that each anchored root is covered byte-exactly by an RFC 3161 timestamp token whose signed time is shown. This page does not validate the timestamp authority's CMS certificate chain (an offline page has no trust store), and revocation cannot be checked offline by any tool. To fully validate a token, use the openssl ts commands in README.txt against the raw files in anchors/. The signature proves "made by the holder of the key above"; binding that key to a person happens out of band (contract, key continuity across invoices). Crypto posture: the sender's signing key is software-stored (SoftwareKeySigned), and none of this proves who was physically at the keyboard.