Can we leave?
Not "Can we export?" Everyone can export. The proof is: can another system reconstruct the same organization without H33?
This bundle is not a download. It is a reconstruction substrate. A third party — without access to H33, without our database, without our verifier service — extracts the bundle, builds the open-source verifier binary, replays each case to its SACRED state_id byte-identically, and re-aggregates the Organizational Twin. If their result matches the bundle's enterprise_*.json files, the institution has crossed the portability boundary. That is the organizational form of "the canonical event log reproduced the snapshot byte-identically."
—
⬇ Download enterprise_bundle.tar.gz"A third party can reconstruct the Organizational Twin from the exported bundle WITHOUT access to the originating system."
That is the portability equivalent of: the canonical event log reproduced the snapshot byte-identically. Not "bundle generated." Not "archive downloaded." Match between independent reconstruction and the bundle's enterprise_*.json = portability proven.
Build the independent verifier
The verifier binary is open-source. The third party builds it themselves — no H33 access required:
git clone <scif-backend repo> cd scif-backend cargo build --release --bin h33-independent-canonical-replay
Verify every SACRED state_id reproduces byte-identically
For each case_id in the bundle, extract cases/{case_id}/submission.tar.gz, then extract evidence_package.tar.gz inside it, then run the verifier against events.json. The verifier's reported state_id must equal the SACRED value in enterprise_replay_metadata.json. Any mismatch stops the process — the bundle is either tampered with or the verifier build is broken.
Re-aggregate the Twin
Walk the per-case reports inside each submission and produce your own version of each enterprise_*.json. The algorithm is documented in reconstruction_runbook.md:
- Walk authority_* events → Authorities
- Union responsibility_report.aggregate → Responsibilities
- Group policy_*/model_* events → Policies/Models
- Concatenate decision_chain/loss_chain/claim_chain → Decisions/Consequences
- Concatenate finding_report.findings → Findings
- Merge & sort timeline events globally → Timeline
Compare your reconstruction against the bundle
Your re-aggregated objects should match the bundle's enterprise_*.json structurally one-to-one. Match → portability proven. Disagreement → itself evidence: a Reality Gap in the bundle, the verifier, or the runbook. The runbook documents what to do in either case.
What proving this proves
- The institution survives the vendor. H33 disappears tomorrow; this bundle still reconstructs the enterprise.
- The reconstruction is independent. No H33 endpoint, no H33 database, no H33 staff. Just the bundle + the open-source verifier.
- The bundle is the receipt. Same posture the case-level submission.tar.gz takes for a single regulator package — now scaled to the whole enterprise.
Eric LOCKED: "That is the organizational form of the H33-74 portability thesis. Evidence survives systems."
After Module 4 → Layer 3
This is the final module of the Evidence Operating System v1. With Timeline · Relationships · Twin · Portability shipped, the layer-completion criterion holds: the next bottleneck is no longer inside the OS. It is in proving which markets care.
The next focus shifts upward into the vertical applications built on this substrate: