Drop a Buyer-Review Pack below. Your browser recomputes every sealed hash locally — this page makes no network requests, needs no account, and stores nothing. You can verify that claim yourself: open your browser's developer tools and watch the network panel stay empty.
It proves: the pack is internally consistent and has not been altered since sealing. Every certificate's hash covers the previous seal, so changing any past entry — a status, a target, one character of evidence — breaks every hash after it. If the stamp reads INTACT, the record you are holding is the record that was written, in the order it was written.
It does not prove: that the pack came from AXYVOR or from the organization it names. A consistent chain could be fabricated whole by whoever built the file. Proving origin requires a signature or an external anchor of the chain head, so ask whoever handed you the pack how its origin can be confirmed.
One technical honesty note: evidence values must survive a JSON round-trip to be recomputable. Text, booleans, and whole numbers do. A decimal written with trailing zeros (for example 1.50) is normalized by JSON tooling before it reaches this page and would report as a mismatch. AXYVOR's own sealers avoid such values; a pack that fails only for this reason deserves a second look, not a verdict.
Each certificate seals: sha256(prev_hash ‖ tenant_id ‖ action_type ‖ target ‖ status ‖ evidence ‖ sealed_at)
The first seal's prev_hash is the literal word GENESIS. Evidence is serialized exactly as PostgreSQL's jsonb text form (keys ordered by length then bytes), and timestamps exactly as its timestamptz text form — this page reproduces both, byte for byte, and hashes with the Web Crypto API built into your browser. AXYVOR applies the same formula on its side; the point of this page is that you never have to rely on it.