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.

"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

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.

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.

v0.1.0 release

⬇
h33-issue-submission-v0.1.0-aarch64-apple-darwin
size936,544 bytes  ·  sha3-256d888e22bf26c61d5e9ca9a67c64f28cf070d76de3193a494f089cee8bd3819e3
Issuer ⬇
⬇
h33-verify-submission-v0.1.0-aarch64-apple-darwin
size820,672 bytes  ·  sha3-256ac2f70c3d0af24d7c36e3da88d5bc3876a4bee3044e57c232d8f0f593d30bff9
Submission Verifier ⬇
{ }
scope-manifest-v1.schema.json
canonical JSON Schema for the scope manifest · publishable · alphabetical field order · determinism contract
Schema ⬇
{ }
sample-submission-claim-84711.regulatory_submission.json
a real signed submission against the canonical-continuity tenant · CFPB inquiry · 2 decisions · 51 KB
Sample ⬇
↺
sample-verify-output.txt
what the submission verifier prints when you run it against the sample — captured PASS output with embedded TDA loop verdicts
Output ⬇
≡
release_manifest.json
all hashes · substrate-reuse test · 6 checks · 5 consumption patterns · v0.2 deferrals
Manifest ⬇
≡
README.md
eleven-command quick start · how to issue your own · honest v0.1 caveats
README ⬇

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/

Run the loop

chmod +x h33-verify-submission-v0.1.0-aarch64-apple-darwin
chmod +x h33-verify-attestation-v0.1.0-aarch64-apple-darwin
chmod +x h33-independent-canonical-replay-v0.1.0-aarch64-apple-darwin

./h33-verify-submission-v0.1.0-aarch64-apple-darwin \
    --submission sample-submission-claim-84711.regulatory_submission.json \
    --bundle tenant_insurance_claim_44962d9b-25f5-5622-bd9a-98d5580bb8a2_enterprise_bundle.tar.gz \
    --attestation sample-attestation-claim-84711.tda_v1.json \
    --verifier-binary h33-independent-canonical-replay-v0.1.0-aarch64-apple-darwin \
    --attestation-verifier h33-verify-attestation-v0.1.0-aarch64-apple-darwin
Expected output — six checks (with the TDA loop running inside check 3)
  • 1 ✓ Scope manifest PQ signatures verify + officer fingerprint internally consistent
  • 2 ✓ Artifact hash anchors match (bundle · attestation · verifier · bundle size)
  • 3 ✓ TDA loop verification PASS — delegates to h33-verify-attestation; bundle + attestation + verifier all agree
  • 4 ✓ Every in-scope decision pinned as eligible in attestation
  • 5 ✓ in_scope_ids structurally present in bundle (no scope smuggling)
  • 6 ✓ scope_window consistent with bundle timeline (no time-window smuggling)
  • → OVERALL: PASS ✓ — submission + bundle + attestation + verifier all agree. No H33 contact required.

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.

Honest v0.2 deferrals