Evidence Bundles
These are real H33 evidence bundles. Each one is a self-contained file — JSON with embedded cryptographic signatures, hash chains, policy commitments, and citations. You can download them, run the verifier against them, and confirm the verdict yourself.
No login. No license. No H33 contact required during verification.
How to Verify a Bundle
- Download the verifier from /downloads/ (Apache 2.0, ~3 MB).
- Download one of the bundle files below.
- Run
h33-verifier verify path/to/bundle.json. - Read the verdict: PASS, FAIL, or INCONCLUSIVE.
The verifier does not phone home. It does not check for updates. It does not need a license. It reads the bundle bytes, validates the cryptographic signatures, replays the hash chain, and confirms the eight Evidence Controls.
Available Bundles
claim_84711.json — Loss Exposure Decision
Insurance claim analysis · bond default · attested 2026-06-04 · v0.2.0-alpha-1 preview bundle
A senior claims analyst was asked: what is the loss exposure on claim 84711? The system ran an analysis over three loan tranches totalling $1.24M and returned an estimated loss exposure of $487,000 with three citations into the source evidence.
The bundle wraps the question, the answer, the authority that signed it, the model fingerprint, the corpus pin, the citations, and the supporting documents — each with its own signature and hash chain. The result is a portable artifact a regulator or reinsurer can verify without contacting H33.
- File
- claim_84711.json
- Size
- 14.6 KB
- Bundle hash
- 7e9f3c1d4a8b2e5f6a91d3c8b2e7f4a91d3c8b…
- Bundle ID
- bundle-9170985d5e1f665413d49a75aed4471ed…
- Signatures
- ML-DSA-65 · FALCON-512 · SLH-DSA-128f
- Evidence controls
- 8 (PEPB, DTMF, TBA, CAB, PDR, CIB, EA, RCB)
- License
- Demonstration bundle, CC0
What You Should See
When you run the verifier against claim_84711.json, the output should look like this:
bundle_id: bundle-9170985d5e1f665413d49a75aed4471ed…
bundle_hash: sha3_384:7e9f3c1d4a8b2e5f6a91d3c8b2e7f4a91d3c8b…
signatures: 3/3 verified
ML-DSA-65 ........ ✓
FALCON-512 ....... ✓
SLH-DSA-128f ..... ✓
evidence controls: 8/8 verified
EC1 PolicyBind ............... ✓
EC2 ModelFingerprint ......... ✓
EC3 AuthorityBind ............ ✓
EC4 CalibratedAbstention ..... ✓
EC5 PipelineDag .............. ✓
EC6 CorpusBind ............... ✓
EC7 EvidenceAttestation ...... ✓
EC8 ResultCitationBind ....... ✓
h33 contacted during verification: NO
The last line is the load-bearing one. The verifier ran end-to-end and reached a PASS verdict without making any network call to H33. That is the portability claim, expressed as verifier output.
About the Bundle Format
H33 evidence bundles are versioned JSON documents. Each bundle carries eight Evidence Controls — the discrete cryptographic commitments that bind a result to its policy, model, authority, corpus, pipeline, citations, and supporting evidence. The eight controls plus three signature families is what makes a bundle portable: a third party can validate every commitment using only the bundle, the published verifier, and the published conformance vectors.
The bundle format and verifier semantics are stable across the v0.2 preview series. Production bundles carry real PQ signatures from customer-controlled HSMs; the demo bundles linked above use deterministic placeholder signatures suitable for demonstrating verifier behavior.
More Bundles Coming
Additional demonstration bundles will be added here over time — AI governance decisions, federal substrate runs, regulatory submission examples, cyber-insurance HATS attestations, BitBonds lifecycle events. The current single bundle is sufficient to demonstrate the verifier surface end to end.
Get Started
The fastest way to understand H33 is to verify a bundle yourself.
Download the verifier Download the bundle About the Portability Verifier View a sample Trust CardBundle + Attestation + Submission + Verifier all agree. No H33 contact required.