Schedule DemoLaunch H33
How H33 Works
Platform OverviewUnder the HoodArchitecture
Cryptography
Post-Quantum CryptographyFHE-IQZero-Knowledge ProofsAPIs & Documentation
APQC — PQ MigrationH33-Key — Machine IdentityH33-You — Human IdentityH33-API-G — Governed API AuthorityAgent-008 — AI GovernanceH33-74 — Portable ProofH33-PQ-Time — Temporal EvidenceH33-Verify — Offline VerificationH33-Recovery — Ransomware RecoveryHATS — Cyber InsuranceH33-GPIS — Federal ProcurementH33-AIR — Wireless TrustH33-Swarm — Governed Adversarial AIH33-PQ-Video — Meeting AuthorityH33-GIT — Governed LineageView All Products
Federal & GovernmentFinancial ServicesHealthcareLaw FirmsAI Agent SecurityPost-Quantum MigrationDigital Asset ContinuityPaymentsCyber Insurance
Live DemosProof LabBenchmarksIndependent VerificationStandardsHICSPQ-VerifiedSecurity & TrustSOC 2 Report Request
DocumentationSDKs & ToolsAPI ReferenceWhite PapersResearchBlogPatentsFAQCompanyContact
Pricing
Log InGet API Key
H33
h33-submission · v0.1.0 · released 2026-06-04 · Layer 3 vertical #2

Submission + bundle + attestation + Portability Verifier — four artifacts agree without contacting H33.

This exists because evidence a regulator cannot independently re-verify is worthless: a Submission bundles the scope manifest, the H33-74 evidence bundle, the attestation, and a Portability Verifier so the recipient can confirm the facts offline, trusting no one.

"A regulator downloads Submission + Bundle + Attestation + Verifier and independently verifies the submission without contacting H33, the submitter, or any third-party vendor." — Eric, June 4 2026

A Portable Regulatory Submission is a firm-signed evidence artifact a regulator can independently verify offline — not a finding of compliance or regulatory approval, which remain the regulator's to determine. The TDA v0.1 release proved three artifacts agree without H33: bundle + attestation + Portability Verifier. This release adds a fourth: a firm-signed regulatory submission that binds a specific (regulator, inquiry, bundle, attestation, Portability Verifier) tuple at a specific moment in time. The regulator's submission verifier runs six structural checks; the TDA loop runs inside it. Same substrate. Same Q0/Q0.5. One new consumer class.

This is an Attestation & Receipts expression of H33-74, which produces the portable 74-byte post-quantum evidence primitive. It does not render the verdict (Verification), monitor controls (HATS), or govern the agent (Agent-008).

Constitutional invariants this release embodies

Q0 — Who bears risk? Never H33. The firm signs the transmittal. H33 is not in the submission path and hosts no submission registry.

Q0.5 — Who owns the judgment? Always the regulator. The submission verifier surfaces structural verdicts. It never asserts compliance, recommends action, or judges the firm's decisions.

Money quote — Submission ≠ Adjudication. Parallel to Attestation ≠ Underwriting. Submission is a structural act the firm performs against the regulator. Adjudication is the regulator's act. H33 ships infrastructure for the first; H33 does not participate in the second.

The four-artifact loop, end to end

A regulator needs four downloads. Each comes from a different surface; together they prove agreement without H33, the submitter, or any third-party vendor.

1 · Submission
Firm-signed scope manifest
From this page (sample) or transmitted by the firm
2 · Bundle
Enterprise portability bundle
From /workspace/portability/ or transmitted by the firm
3 · Attestation
Signed tda_v1 JSON
From /attestation/ or transmitted by the firm
4 · Portability Verifier
Canonical-replay binary
From /verifier/

Substrate-reuse claim — the platform argument

This release reuses the existing Bundle + Attestation + Portability Verifier triple unchanged. It adds two primitives: the scope manifest schema and the submission verifier binary. Constitutional layer Q0 + Q0.5 carries forward unchanged.

TDA proved the carrier consumption pattern (Layer 3 vertical #1). Regulatory Submission v0.1 proves the regulator consumption pattern (Layer 3 vertical #2). Same substrate. Same constitutional rules. Auditor (#3), Acquirer (#4), and Governance team (#5) are the next consumer classes — each will inherit the same Q0/Q0.5 and consume the same substrate.

When to use it — and when not to

Use this submission pair when a regulator has opened an inquiry and you must hand over evidence they can verify independently and offline — no live API, no trust in H33, no trust in the submitter. It is built for the moment the firm proves what was submitted and that the in-scope decisions replay to their canonical state.

Do not reach for it when you want a compliance verdict or an approval. A submission is portable evidence; it is not a finding of compliance and does not by itself constitute regulatory approval. That is adjudication — the regulator's act. For continuous control monitoring use HATS; to govern the AI agent's decisions use Agent-008; for the independent replay verdict see Verification.

The five questions this page answers

Frequently asked questions

Does a passing submission mean the firm is compliant or approved?

No. A PASS from the submission verifier is a structural verdict — signatures verify, hash anchors match, in-scope decisions are pinned, the bundle replays to its canonical state. It is portable evidence a regulator can independently verify. It does not by itself constitute regulatory approval, a compliance finding, or a legal conclusion. Adjudication is the regulator's act; H33 ships infrastructure for the submission but does not participate in the adjudication.

How is it verified without contacting H33?

The regulator downloads the four artifacts and runs the submission verifier locally. It re-checks the post-quantum signatures, re-computes the artifact hash anchors, and delegates the bundle+attestation+verifier replay to the attestation verifier — all offline against the published schema. Nothing in the loop calls H33, the submitter, or any third-party vendor. The cryptography (post-quantum signatures, SHA3, JCS canonicalization) are external standards the substrate uses, not H33 inventions.

How does this differ from Verification, HATS, and Agent-008?

H33-74 produces the submission artifact. Verification renders the independent replay verdict on it. HATS records and monitors controls over time and does not produce this artifact. Agent-008 governs the AI agent decisions captured in the bundle and does not verify the submission.

Honest v0.2 deferrals