# h33-submission v0.1.0 — Portable Regulatory Submission v0.1

Layer 3 vertical #2. Same Q0/Q0.5 constitutional layer as the TDA
release. Same substrate (Bundle + Attestation + Portability Verifier). Adds only
the Scope Manifest and the Submission Verifier.

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

This release ships the binaries that satisfy that success criterion.

## What's in this release

| File | Purpose |
|---|---|
| `h33-issue-submission-v0.1.0-aarch64-apple-darwin` | The firm's CLI for issuing a signed scope manifest + emitting a `regulatory_submission` event |
| `h33-verify-submission-v0.1.0-aarch64-apple-darwin` | The regulator's CLI for running the 6 structural checks |
| `scope-manifest-v1.schema.json` | Canonical JSON Schema for the scope manifest |
| `sample-submission-claim-84711.regulatory_submission.json` | A real signed submission against the canonical-continuity tenant |
| `sample-verify-output.txt` | What you should see when you run the submission verifier against the sample |
| `release_manifest.json` | Hashes + capabilities + 6 checks + v0.2 deferrals |
| `README.md` | This file |

You also need:

- The H33 Portability Verifier — `h33-verifier v0.1.0` at https://h33.ai/verifier/
- The TDA attestation verifier — `h33-verify-attestation v0.1.0` at https://h33.ai/attestation/
- An enterprise bundle — for the sample, the canonical-continuity tenant bundle at https://h33.ai/workspace/portability/bundles/
- A TDA attestation — for the sample, https://h33.ai/attestation/v0.1.0/sample-attestation-claim-84711.tda_v1.json

## Quick start — close the second loop in eleven commands

```bash
# 1. Fetch the four artifacts: submission · bundle · attestation · Portability Verifier
curl -O https://h33.ai/submission/v0.1.0/h33-verify-submission-v0.1.0-aarch64-apple-darwin
curl -O https://h33.ai/submission/v0.1.0/sample-submission-claim-84711.regulatory_submission.json

curl -O https://h33.ai/attestation/v0.1.0/h33-verify-attestation-v0.1.0-aarch64-apple-darwin
curl -O https://h33.ai/attestation/v0.1.0/sample-attestation-claim-84711.tda_v1.json

curl -O https://h33.ai/verifier/v0.1.0/h33-independent-canonical-replay-v0.1.0-aarch64-apple-darwin
curl -O https://h33.ai/workspace/portability/bundles/tenant_insurance_claim_44962d9b-25f5-5622-bd9a-98d5580bb8a2_enterprise_bundle.tar.gz

# 2. Make the binaries executable
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

# 3. Run the loop
./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
```

You should see:

```
✓ Officer fingerprint internally consistent
· No --trusted-officer-fingerprint supplied (v0.1 dev posture — accept any)
✓ Canonical payload hash matches declared value
✓ All 3 scope manifest PQ signatures verify (ML-DSA-65 · FALCON-512 · SLH-DSA-128f)
✓ Bundle hash anchor matches
✓ Attestation hash anchor matches
✓ Verifier binary hash anchor matches
  [tda] ✓ Issuer fingerprint internally consistent
  [tda] ✓ Canonical payload hash matches declared value
  [tda] ✓ All 3 PQ signatures verify (ML-DSA-65 · FALCON-512 · SLH-DSA-128f)
  [tda] ✓ Bundle hash anchor matches
  [tda] ✓ Verifier binary hash anchor matches
  [tda] ✓ Decision decision_loan_84711_approval replays to SACRED state_id
  [tda] ✓ Decision decision_loan_84711_recommendation replays to SACRED state_id
  [tda] OVERALL: PASS ✓ — bundle + attestation + verifier all agree. No H33 contact required.
✓ TDA loop verification PASS (h33-verify-attestation)
✓ All 2 in-scope decisions pinned as eligible in attestation
✓ in_scope_ids structurally present in bundle
✓ scope_window consistent with bundle timeline

OVERALL: PASS ✓ — submission + bundle + attestation + verifier all agree. No H33 contact required.
```

That output is the close of Eric's success criterion. You did not contact
H33, the submitter, or any third-party vendor at any step.

## Issue your own submission

To bind your tenant to a regulator inquiry:

```bash
./h33-issue-submission-v0.1.0-aarch64-apple-darwin \
    --bundle path/to/enterprise_bundle.tar.gz \
    --attestation path/to/attestation.tda_v1.json \
    --verifier-binary path/to/h33-independent-canonical-replay \
    --regulator-identifier "US Consumer Financial Protection Bureau" \
    --inquiry-reference "CFPB-2026-INQ-00471" \
    --officer-name "Jane Doe" \
    --officer-office "Chief Risk Officer" \
    --in-scope-decisions decision_a,decision_b \
    --in-scope-findings finding_x \
    --signing-key-dir ~/.h33/firm-keys \
    --output my-submission.regulatory_submission.json
```

On first run, the issuer generates a fresh PQ keypair into the
`--signing-key-dir`. Subsequent runs reuse the same key, which is what
keeps the **determinism property** intact.

## Six regulator-side checks (what the submission verifier runs)

| # | Check | Failure mode |
|---|---|---|
| 1 | Scope manifest PQ signatures (ML-DSA-65 + FALCON-512 + SLH-DSA-128f) + officer fingerprint internal consistency | Forged or repudiated transmittal |
| 2 | Artifact hash anchors (bundle · attestation · Portability Verifier · bundle size) match scope manifest pins | Wrong artifact or tampering in transit |
| 3 | TDA loop verification (delegated to `h33-verify-attestation`) — Bundle + Attestation + Portability Verifier all agree | TDA loop failure — substrate inconsistent with attestation |
| 4 | Cross-check: every in-scope decision is also pinned as eligible in the attestation | Decision claimed in scope but not pinned in attestation |
| 5 | `in_scope_ids` structurally present in bundle | Scope smuggling — claimed scope mismatches actual contents |
| 6 | `scope_window` consistent with bundle timeline (in-scope decision times within window) | Time-window smuggling |

Any single check failing flips OVERALL to FAIL. Each check is structurally
observable. No interpretation. No recommendation. No compliance score.

## Substrate-reuse claim

This release reuses the existing Bundle + Attestation + Portability Verifier triple
unchanged. It adds two primitives:

- the **scope manifest** schema (this directory's
  `scope-manifest-v1.schema.json`)
- the **submission verifier** binary

That's the substrate-reuse property Eric locked after the v1 design
memo landed:

> *"You're no longer proving technology. You're proving that the same
> portability substrate can support multiple consumer classes without
> changing the constitutional rules. That's a stronger argument than any
> individual product."*

TDA proved the carrier consumption pattern. Regulatory Submission v0.1
proves the regulator consumption pattern. Same substrate. Same Q0/Q0.5.

## What this release does NOT do (Q0.5)

The submission verifier surfaces structural verdicts. It never judges whether the
submitted decisions complied with any statute, regulation, or supervisory
expectation. The regulator forms the regulatory judgment. H33 publishes
no regulator-acceptance indicator, no statute-to-readings mapping, no
recommended regulatory action.

## What H33 does NOT do (Q0)

H33 does not receive the submission. H33 is not in the transmittal
channel. H33 hosts no submission registry. H33 cannot be on the legal-
process hook for a submission it never received. The firm transmits to
the regulator directly (regulator portal · email · SFTP · hand-delivered
drive · whatever the regulator accepts).

## Honest v0.1 caveats

- **Multi-platform:** darwin-arm64 binaries only. Linux + darwin-x86 in v0.2.
- **Dev firm-side signing key:** the issuer generates a fresh PQ keypair per `--signing-key-dir`. Production submissions require a v0.2 key ceremony — until then submissions have demonstration value, not legal weight.
- **No release signing:** the binaries themselves are hash-anchored only; PQ-signed releases in v0.2.
- **No revocation registry:** v0.1 submissions cannot be revoked once transmitted. v0.2 adds revocation.
- **No supplemental workflow detail:** `supersedes` and `supplements` fields exist on the schema; workflow semantics land in v0.2.
- **No multi-regulator harmonization conventions:** v0.1 ships the substrate; portal adapters and cross-jurisdictional templates await regulator-side feedback.

## Hashes (for the lazy)

```
h33-issue-submission-v0.1.0-aarch64-apple-darwin   d888e22bf26c61d5e9ca9a67c64f28cf070d76de3193a494f089cee8bd3819e3
h33-verify-submission-v0.1.0-aarch64-apple-darwin  ac2f70c3d0af24d7c36e3da88d5bc3876a4bee3044e57c232d8f0f593d30bff9
scope-manifest-v1.schema.json                      717b6b54425546bfa23ae2157926f55384cef023b77cbf323c81140236e0fefe
sample-submission-claim-84711.regulatory_submission.json  8364c97f9e091b19cdd2d4d2b83e8e1283ea1c3209587d610e501a4cca61be88
sample-verify-output.txt                           c40160553c556f612982f2f13078c090914f0d81a8f8737e9bdc57a115de7574
```

— h33-submission v0.1.0 · 2026-06-04