H33 Portability Verifier.
The H33 Portability Verifier is the open-source binary any third party can download, build from source, and run offline to confirm that an H33 enterprise bundle replays to its expected SACRED state_id byte-identically. It is the load-bearing artifact of the portability category — the surface where independent verification becomes operational rather than aspirational.
"How does the verifier verify if H33 disappears?"
It is a single binary. It carries its own logic. It does not phone home. It does not require an API key. It does not require H33 to be available, online, or in business. Three lines of shell verify a real enterprise bundle today.
What the Portability Verifier verifies
Structural replay. Given a canonical event log and a manifest pinning the expected SACRED state_id, the verifier walks the events deterministically through the replay engine, computes the resulting state_id, and confirms it matches the pinned value byte-identically. It then performs five additional structural checks: policy version references resolve, model version references resolve, decision lineage resolves, decisions were made while authority was live, and post-quantum signatures over each event verify.
Output is a structured JSON report with two load-bearing fields: overall_pass (boolean) and determination (a sentence). PASS means the bundle replays. FAIL means it does not. There is no "best effort" verdict.
What makes verification independent
How a third party uses it
Download the binary from /verifier/v0.1.0/. Confirm its SHA3-256 against the published hash. Run it against an enterprise bundle. Read the JSON verdict.
No support ticket. No vendor approval workflow. No SaaS subscription. The category H33 ships is portable verification infrastructure; this binary is the entry point to it.
Where this sits: independent Verification
The Portability Verifier is the reference actor of Verification — it independently renders the verdict on a bundle it did not produce, reproducing the SACRED state_id and validating the post-quantum signatures. It consumes an artifact and returns PASS or FAIL. 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 whether a decision was authorized (that is Agent-008).
A PASS means the bundle reproduces byte-identically and its signatures validate — it does not mean the underlying system is secure, that the decision was correct or fair, or that anything is compliant or lawful. That scope is what makes an independent verdict meaningful. The three PQ families are an AND-gate: ML-DSA-65 (FIPS 204), FALCON-512 (FN-DSA / FIPS 206 draft), and SLH-DSA-SHA2-128f (FIPS 205) must all validate; two of three would be a false grant.
FAQ
What does a passing verdict mean — and what does it NOT mean? PASS (overall_pass: true) means the bundle replays to its pinned SACRED state_id byte-identically and its PQ signatures validate. It does not mean the system is secure, the decision correct or fair, or anything compliant.
Is the verifier independent of H33? Yes. It is a single offline binary with public keys shipped inside the artifact; it makes zero network calls at verify time. If H33 is offline, sanctioned, acquired, or sunset, the verdict still reproduces.
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 binary only reproduces and validates.
Is the PASS result hardcoded? No. The verdict is computed from the artifact: the replay engine recomputes the state_id from the event log and compares it to the pinned value, and five structural checks plus per-event signature verification each contribute. Any tampered event breaks the replay and yields FAIL — there is no “best effort” verdict.