Portable Regulatory Submission.
A Portable Regulatory Submission is a firm-signed scope manifest binding a specific regulator inquiry, a specific bundle, a specific attestation, and a specific verifier binary into a single transportable artifact. The regulator runs six structural checks independently, without contacting H33, the submitter, or any third-party vendor. It is portable evidence a regulator can verify — not a finding of compliance or regulatory approval, which remain the regulator's to determine. It exists because a regulator must be able to re-verify a submission independently and offline, long after the systems that produced it are gone.
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).
"What is a Portable Regulatory Submission in one sentence?"
A firm-signed JSON manifest that turns the three-artifact TDA loop into a four-artifact regulator loop. The artifact survives every layer of vendor risk in the chain. Even if the submitter dissolves, the regulator can still verify what was submitted.
The four-artifact loop, end to end
A regulator needs four downloads. Each comes from a different surface; together they prove agreement without any vendor in the loop.
tda_v1 document attesting specific decisions in the bundle.The submission verifier delegates the bundle+attestation+verifier loop to the attestation verifier, then runs four submission-specific structural checks: artifact hash anchors, in-scope decision pinning, scope-IDs present in the bundle, and scope-window consistency with the bundle timeline. Six checks total. The TDA loop runs inside check three.
The money quote — Submission ≠ Adjudication
"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 submission verifier surfaces structural verdicts only. It never asserts compliance, recommends action, or judges the firm's decisions. The regulator always owns the regulatory judgment. H33 ships the substrate; the verdict is the regulator's.
When to use it — and when not to
Use a Portable Regulatory Submission when a regulator has opened an inquiry and you need to hand over evidence they can verify independently, offline, without trusting H33, without trusting you, and without a live API. It is built for the moment the firm must prove what was submitted and that the underlying decisions replay to their canonical state — evidence that survives even if the submitter dissolves.
Do not reach for it when you want a compliance verdict, an approval, or a legal opinion. A submission is portable evidence; it is not a finding of compliance and does not by itself constitute regulatory approval. That determination is the regulator's alone. If you need continuous monitoring of controls, that is HATS; if you need to govern the AI agent's decisions, that is Agent-008; if you need the independent replay verdict, that is Verification.
The five questions this page answers
Download the submission issuer + verifier and run the six structural checks on a real CFPB-style fixture.
Get the Submission Pair → All Five Surfaces →Frequently asked questions
Does a Portable Regulatory Submission mean the firm is compliant or approved?
No. The submission is portable evidence a regulator can independently verify. It proves what was submitted and that the underlying decisions replay to their canonical state. It does not by itself constitute regulatory approval, a compliance finding, or a legal conclusion. Adjudication — the judgment of compliance — is the regulator's act. H33-74 ships infrastructure for the submission; H33 does not participate in the adjudication.
How is the submission verified without contacting H33?
The regulator downloads the submission, bundle, attestation, and the open-source Portability Verifier, then runs the submission verifier locally. It re-checks the post-quantum signatures, re-computes the artifact hash anchors, and replays the bundle to its canonical state — all offline against the published scope-manifest-v1 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 is this different from Verification, HATS, and Agent-008?
H33-74 produces the portable submission artifact. Verification renders the independent replay verdict on it. HATS records and monitors controls over time; it does not produce this artifact. Agent-008 governs the AI agent decisions that populate the bundle; it does not verify the submission. This page is only about the portable evidence artifact and the boundary each neighbor owns.
What if H33 disappears — does the submission still verify?
Yes. That is the point of a portable artifact. The bundle replays offline, the Portability Verifier is open-source, and the post-quantum signatures verify against published standards indefinitely. Even if H33 or the submitter ceased to exist, the regulator can still verify what was submitted from the artifact alone.