Trust Card

One page. Six fields. Hand it to anyone.

A Trust Card is a compact, printable artifact that summarizes the portability claims for any H33 evidence bundle. It is designed to be handed to a regulator, auditor, board member, acquirer, or insurer who has thirty seconds and needs to know: can I verify this myself.

The answer is always yes. The Trust Card tells you how.

What a Trust Card Looks Like

What the Six Fields Prove

The Trust Card is six fields because every claim H33 makes about an evidence bundle reduces to those six checks.

Bundle hash

The cryptographic fingerprint of the bundle file. Whoever holds a Trust Card and the bundle file can recompute the hash locally and confirm the bundle has not been altered since it was attested.

Verifier verdict

The output of h33-verifier when run against the bundle. PASS means all eight Evidence Controls (PolicyBind, ModelFingerprint, AuthorityBind, CalibratedAbstention, PipelineDag, CorpusBind, EvidenceAttestation, ResultCitationBind) verified. FAIL means at least one did not. INCONCLUSIVE means a required check could not run.

Signatures

Three NIST-standard post-quantum signature families: ML-DSA-65 (FIPS 204), FALCON-512, SLH-DSA-128f (FIPS 205). The bundle is signed under all three. An adversary would need to break all three families to forge an H33 attestation — and FALCON and SLH-DSA rely on independent mathematical assumptions.

Anchor

The on-chain transaction that committed the bundle hash to a public blockchain. The Trust Card carries the transaction hash, block, and confirmation count so anyone can query the chain directly and confirm the commitment exists.

Conformance vectors

The published test vectors that prove the verifier produces byte-identical output across implementations. The vectors are how a third party knows that the verifier they downloaded behaves the same as the verifier H33 published.

Verifier binary

The exact version of h33-verifier the Trust Card was generated against. Open source under Apache 2.0. SHA256 lets the recipient confirm they ran the same binary. No license check, no network call, no H33 contact required.

How to Generate a Trust Card

Every H33 bundle generates a Trust Card automatically. The Trust Card is a derived artifact — it is computed from the bundle, the verifier output, and the anchor record. You do not need to ask H33 to generate one; you can produce one from any bundle, verifier binary, and on-chain record yourself.

1. Run h33-verifier verify bundle.json against the bundle file.
2. Capture the verdict, signature results, and EC pass/fail counts from verifier output.
3. Query the chain at the anchor txid recorded in the bundle's anchor sidecar.
4. Look up the conformance vector SHA from h33.ai/conformance/.
5. Render those six fields on a page.

That is the entire procedure. The Trust Card is a presentation of facts that already exist on the bundle, the chain, and the verifier output. Nothing about it depends on H33 being reachable.

Why It Matters

Regulators and auditors are accustomed to receiving attestation letters that say "trust us." A Trust Card says the opposite: don't trust us; verify it yourself in five minutes using a binary we don't operate and a blockchain we don't control.

That inversion is the point of every artifact H33 ships. The Trust Card is the smallest possible expression of it — six fields, one page, no narrative, no marketing. Just the facts that let a third party reach the same conclusion the issuer reached, without asking the issuer.

Bundle + Attestation + Submission + Verifier all agree. No H33 contact required.