One page. Six fields. Hand it to anyone. Load any H33 bundle. Compute its hash in your browser. Render the card. Tamper one byte. Watch verification fail. Nothing mocked.
This page loads /bundles/claim_84711.json by default. You can also paste any other H33 bundle. The page then:
(1) Computes a real SHA-256 hash of the bundle bytes in your browser using Web Crypto. (2) Parses the bundle to extract the six Trust Card fields. (3) Renders the card live. (4) Lets you tamper any byte and watch the card flip to FAIL.
This is a real verifier-shape demonstration. The page makes no network call beyond fetching the bundle file. H33 is not contacted during any of the computation. This page uses a public demo key with no issuer verification, so its receipts carry no authenticity: they show internal consistency with the key they carry, not that H33 issued them.
A Trust Card is a one-page, human-readable rendering of the portable evidence artifact that H33-74 produces — six fields drawn from an H33 bundle whose hash can be re-checked in the browser.
Why it exists. Evidence that only its originating system can confirm is not evidence. The Trust Card exists so proof of what happened can be handed to any party — a regulator, an auditor, a counterparty — (independent re-verification not yet available for production receipts).
What it is NOT. The card is the evidence, not the verdict. Rendering it is not the independent verdict (that is Verification), not operational monitoring (that is HATS), and not the governance decision (that is Agent-008). H33-74 produces the artifact; Verification renders the verdict on it. The local check here compares stated vs. computed hashes and is tamper-evident — it demonstrates the receipt is re-checkable, it does not stand in for the authoritative verdict.
Waiting for bundle…
Public demo key · no issuer verification. A passing (VALID) result shows the receipt is internally consistent with the public key it carries. It carries no authenticity: it does not show that H33 issued the receipt.
The whole point of a Trust Card is that tampering is detectable. The verifier compares the stated hash against the computed hash. Edit any byte of the bundle below and the computed hash will diverge from the stated hash. The verifier will return FAIL. The card will repaint with a red FAIL stamp.
This is what a regulator's local verifier does the moment a bundle arrives. No network call. Just hash arithmetic.
It is a one-page rendering of the portable evidence artifact H33-74 produces. It is the evidence, not the verdict: it does not render the independent verdict (that is Verification), does not monitor operations (that is HATS), and does not make the governance decision (that is Agent-008).
H33-74 produces the evidence the card shows; Verification independently renders the verdict on it. The in-browser hash check here proves the bundle is re-checkable and tamper-evident; deciding whether the evidence should be trusted, against policy, is Verification's role on a separate axis.
In your browser (hash check only). This page computes the bundle hash in your browser via Web Crypto and compares it to the stated hash — no upload, no H33 contact. Tamper one byte and the check fails, which is why the result is tamper-evident. The production verifier binary does the same against SHA3-256; the PQ signature families in the envelope (ML-DSA, FALCON, SLH-DSA) are external NIST-track standards H33 implements.
Use it when you need portable proof you can hand to an outside party. Do not use it when you need the independent verdict on whether that evidence should be trusted — use Verification instead; when you need to record and monitor a control over time — use HATS instead; or when you need to govern who may act — use Agent-008 instead. The card is the evidence, not the verdict on it.
H33-74 owns and produces the portable 74-byte post-quantum evidence primitive this card renders. Verification renders the verdict · HATS records and monitors · Agent-008 governs the decision.