Verify portable artifacts independently.
Bundle + Attestation + Submission + Verifier all agree. No H33 contact required.
A carrier, auditor, regulator, PE partner, or CISO downloads this binary, points it at an H33 enterprise bundle, and confirms the bundle replays to its SACRED state_id byte-identically — with no H33 contact, no database access, no vendor service call. The artifact survives us. "H33 issued the attestation. H33 is not required to verify the attestation."
Q0 — Who bears risk? Never H33. This binary bears the risk of verifier correctness — same input → same output, byte-identically. Nothing else.
Q0.5 — Who owns the decision? Always the decision owner. The verifier surfaces structural replay verdicts. It never judges whether a decision was wise, correct, fair, lawful, or compliant.
Verify a bundle right now.
Drop an H33 evidence bundle below — or use the demo bundle claim_84711.json. The verifier runs entirely in your browser. No network call to H33. You should have a verdict in under 15 seconds.
What's inside a portable artifact.
Click a node to highlight the matching block in the bundle JSON.
Load a bundle above to see its JSON…
Break the bundle five different ways.
Each button mutates one specific field. The verifier produces a different failure mode for each. People remember breaking things more than reading about them.
Verify without H33.
Who needs to be reachable for a verification to succeed?
CUSTOMER H33 INTERNET │ │ │ ├── Bundle ✓ ├── (offline) ├── (optional) ├── Verifier ✓ │ │ └── only for ├── Public keys ✓ │ │ chain └── Conformance vectors ✓ │ │ anchor │ │ fetch ───────────────── ───────────────── ───────────────── All required NOT CONTACTED Optional RESULT: Independent Verification
If H33 is offline, sanctioned, acquired, or sunset, this verification still succeeds. The bundle is the artifact. The verifier reads it. The conformance vectors prove the verifier behaves correctly. Anchor confirmation queries a public chain RPC — and that RPC can be operated by anyone, not just H33.
Six ways verification fails.
A verifier that only emits PASS feels like marketing. A verifier that has a documented set of failure modes — and emits the right one for each tampered input — feels real.
err: signature[0] verify failed expected_digest_sha3_384: a83e...c712 actual_digest_sha3_384: 91f4...c8b2 → bundle modified after signingSee full example →
err: EC-8 ResultCitationBind result_text_hash: ab29...3c8e bundle_text_hash: e4f1...a9d2 → answer text was modifiedSee full example →
err: profile gate refused verifier_profile: federal bundle_profile: commercial → mode mismatch, refuse to verify
err: unsupported algorithm
signature[0].algorithm: "FAKE-256"
allowed: ML-DSA-65, FALCON-512,
SLH-DSA-SHA2-128f
→ reject untrusted algorithm
err: authority expired authority_id: claims-officer-tier-2 not_after: 2025-12-31T23:59:59Z verified_at: 2026-06-07T01:48:00Z → mandate lapsed, advisory FAIL
err: anchor inclusion failed chain: avalanche-fuji tx_hash: 0x83a9...7c2e rpc_says: tx not found at block 47118229 → anchor evidence invalidSee full example →
VERDICT: PASS signatures: 3/3 verified evidence controls: 8/8 verified anchor: confirmed h33 contacted: NOSee full example →
replay_input: bundle_hash + verifier_v0.1.0
replay_output: byte-identical to first run
property: deterministic across machines
and across decades
See full example →
All examples have their own page under /verification/ — each is a documented verifier behavior with the inputs that produce it, the bundle bytes involved, and the exact verifier output.
Verify a portable artifact
H33 no longer distributes a downloadable verifier binary. Verification is available in the browser at the Proof Lab verifier, a separate page which loads a WebAssembly verifier and checks the artifact locally. Your artifact never leaves your browser.
What the Portability Verifier verifies
Structural replay determinism. Five locked checks: policy_version_ref resolves · model_version_ref resolves · decision_lineage resolves · decisions made during active authority · state_id reproduces byte-identically. Plus per-event PQ signature verification (ML-DSA-65 + FALCON-512 + SLH-DSA-128f) with the --verify-signatures flag.
What the Portability Verifier does NOT verify · ever (Q0.5)
The verifier surfaces structural replay verdicts. It does not — and will never — surface judgments about whether a decision was wise · correct · fair · lawful · compliant · likely to hold up in court. Those judgments belong to carriers, auditors, regulators, and acquirers. The verifier provides the substrate; the judgment is theirs.
Honest v0.2 deferrals
- Multi-platform releases (Linux x86_64 · Linux aarch64 · Darwin x86_64)
- PQ-signed release artifacts (release-signing key ceremony required)
- Byte-deterministic builds across machines (containerized toolchain)
- Attestation document format verification (lands when attestation issuance exists)
- CI/CD release automation
- Public-fetchable git tag (gitlab auth currently unauthenticated for the release terminal)
Where this sits: independent Verification
Definition. The Portability Verifier is the reference actor of Verification — it independently renders the verdict on a portable artifact it did not produce, reproducing the bundle and validating its post-quantum signatures. It does not produce the evidence (that is H33-74), does not monitor a running estate over time (that is HATS), does not score control or software maturity (that is HICS), and does not govern the decision (that is Agent-008). It consumes an artifact and returns PASS or FAIL — nothing more.
Why it exists. A verdict is only trustworthy if the vendor can be absent. This tool exists so a carrier, auditor, regulator, or acquirer can download the artifact and reproduce the verdict with H33 not in the loop. When not to reach for it: to watch a system continuously over time use HATS; for a maturity score use HICS; to govern whether an action was authorized use Agent-008; to produce the portable evidence in the first place use H33-74.
What a passing verdict means — and does not. PASS means the artifact reproduces byte-identically and its signatures validate. It does not mean the underlying system is secure, the decision was correct or fair, or the environment is compliant or lawful. The three post-quantum families are an AND-gate: ML-DSA-65, FALCON-512, and SLH-DSA-SHA2-128f must all validate — two of three is a false grant. (ML-DSA / FIPS 204 and SLH-DSA / FIPS 205 are finalized; FALCON-512 is FN-DSA / FIPS 206, still a draft.)
FAQ
What does a passing verdict mean — and what does it NOT mean?
PASS means the artifact reproduces byte-identically and all three PQ signature families validate. It does not certify that the system is secure, that the decision was correct or fair, or that anything is compliant — that boundary is what makes an independent verdict meaningful.
Is the verifier independent of H33?
Yes. You download the binary (or run the in-browser check above) and point it at the bundle; H33 is not contacted. If H33 is offline, sanctioned, acquired, or sunset, verification still succeeds. Only an optional public-chain RPC lookup touches the network, and that RPC can be operated by anyone.
How is Verification different from HATS, HICS, and Agent-008?
Verification renders an independent verdict on an artifact that already exists. HATS records and monitors operational evidence over time; HICS scores maturity; Agent-008 governs the decision. This tool only reproduces and validates — it does not monitor, score, or govern.
How many signatures does this artifact carry, and are they checked?
Three: ML-DSA-65 (FIPS 204), SLH-DSA-SHA2-128f (FIPS 205) and FALCON-512, each signed over the same bytes and each self-verified by the signer before it emits. Two are verified here in your browser. FALCON-512 is not — its reference implementation is C and does not build for wasm32 — so it is reported as present and natively verifiable, never counted as checked. The bundle previously listed three families whose signature bytes were the ASCII placeholder preview-envelope-mldsa-bundle-signing-key-bytes-preview-only, and this page counted the presence of those strings as validation.
Can I make the verifier emit PASS on a bad bundle?
No — the verdict is computed here from the bundle’s own bytes: SHA3-384 over what was served, ML-DSA-65 and SLH-DSA-SHA2-128f verification over those bytes, and every in-bundle digest recomputed. Use the Tamper Challenge above: change one character of the answer text and the hash, both signatures and the answer digest all fail together.
Related in the Verification neighborhood
Verification (the owned capability — renders the independent verdict) · H33-74 (produces the portable evidence this tool verifies) · Verifier CLI · Portability Verifier · Survivability proof