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.
"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.