H33
Portability · H33 Portable Verification Infrastructure

Portable artifacts that survive the originating system.

"What survives if H33 disappears tomorrow?"

H33 produces portable artifacts that remain independently verifiable even if the original software, cloud provider, blockchain, or vendor no longer exists. The substrate's value does not depend on H33 being online, available, in business, or even existing. Portability is the category. Verification is the explanation.

The 15-second test

"What is portability, in one sentence?"

A third party — a regulator, auditor, acquirer, carrier, or CISO — can take an H33 artifact and confirm its provenance, lineage, authority, and replayability without contacting H33. Not "with H33's help." Not "via an H33 API." Without H33. Forever.

What "portable" means here

Most cryptographic systems produce artifacts that depend on the issuing service being online to verify them. Revoke an OCSP responder; cancel a SaaS contract; sunset an API — the artifacts go dark.

H33 artifacts are content-addressed, hash-anchored, post-quantum signed, and verifiable by an open-source binary that runs offline. Nothing about verification requires H33 to be reachable. That property has a name: Portable Verification Infrastructure. The artifact survives us.

The five surfaces of portability

Portability is not a single feature. It is a property the substrate enforces across five surfaces, each independently verifiable, each linked here. Read each in the order below for the full story; jump to any one for the specifics.

1 · The Verifier
H33 Portability Verifier
The open-source binary any third party downloads, builds from source, and runs offline to confirm that an H33 enterprise bundle replays to its SACRED state_id byte-identically. The load-bearing artifact of the category.
2 · The Attestation
Portable Decision Attestation
A signed tda_v1 document binding a bundle, a verifier binary, and a set of decisions into a single transportable artifact. Verifies forever without H33.
3 · The Submission
Portable Regulatory Submission
A firm-signed scope manifest binding bundle + attestation + verifier to a specific regulator inquiry at a specific moment. Six structural checks; the TDA loop runs inside.
4 · The Audit Evidence
Portable Audit Evidence
The substrate-reuse pattern applied to the auditor consumer class. Same bundle + attestation, audit-period bounded. Auditor loop is the next planned consumer surface.
5 · The Bundle
Enterprise Portability Bundle
The underlying transportable .tar.gz that the four artifacts above carry hashes of. Contains the full canonical event log + manifest + SACRED state_id. The substrate's truth layer.

What makes verification independent

The word "independent" here is precise. Not "with our cooperation." Not "via our API." A structural property the substrate enforces:

No vendor contact
Verification initiates no network call to H33 infrastructure.
No vendor key fetch
Public keys travel with the artifact. Fingerprints anchored in a witnessed offline ceremony.
No vendor uptime
A SCIF-deployed verifier with zero internet egress produces identical verdicts to one in commercial cloud.
No vendor existence
If H33 ceases to exist, the verifier still runs. The bundle still verifies. The substrate survives.
No vendor monoculture
Three independent post-quantum families sign every artifact. Breaking one does not break the substrate.
No vendor sunset risk
Verifier source is open. Build is reproducible. Anyone can rebuild forever.

Three loops on the same substrate

The strongest platform argument: different consumer classes verify the same substrate independently and reach the same verdict. H33 has proved it twice and designed the third.

The three loops

  • Decision Attestation · carrier pattern. Bundle + Attestation + Portability Verifier all agree. Verified end-to-end →
  • Regulatory Submission · regulator pattern. Submission + Bundle + Attestation + Portability Verifier all agree. Verified end-to-end →
  • Audit Evidence · auditor pattern. Same substrate, audit-period bounded. Next planned consumer surface. Read the design →

Where this connects

Portability sits above the cryptography H33 has been building for years. Those are how portability holds. Portability is what buyers get.

Verify for yourself · no H33 contact required

Download the H33 Portability Verifier and run it against a real enterprise bundle in eight commands.

Get the Verifier → See the Attestation Loop → See the Submission Loop →