H33
#184 · the capstone · June 3, 2026

First Institutional Death Replay.
The institution died. The evidence survived.

The hero question · LOCKED Eric Beans
"Can we replay a dissolved company?"
"Does evidence survive the institution itself?"
The 5th and final line of the H33 continuity ladder · signed canonical events from before dissolution remain self-sufficient years after the company is gone
Before · the living enterprise
2025
A $4.2M credit default. Claim #84711 filed with the reinsurer.
The substrate from #15 — Replayable Insurance Claim. A real decision, a real loss, a real claim, a real responsibility chain. All signed into the canonical event log.
Death · the enterprise dissolves
2031
The company is liquidated. A court-appointed trustee inherits the open litigation.
The dying root signs one final canonical act: EnterpriseDissolution. After this event, no further events for the tenant are valid. The signed log closes.
After · replay still works
2035
The court trustee replays the chain four years post-death.
No H33. No vendor. No company employees. No company systems. Just the signed events and the verifier. The chain reconstructs. state_id at T=2035: 52a6354d…20dbe.
View the reconstruction JSON ← The continuity ladder Markdown report
Courts Bankruptcy Trustees Court-Appointed Receivers Regulators R&W Insurers Successor Litigators Post-Dissolution Claimants Wind-Down Audit Firms
What was proven · 10-second read

Evidence outlives institutions.

01
The dying enterprise self-signs its own dissolution as its final canonical act. No further events for the tenant are valid after.
02
Four years post-death, replay reconstructs the full chain. Claim #84711 still queryable. Verdict at T=2035: Valid.
03
No H33. No vendor. No company. No employees. Just the signed events and a verifier. The chain is self-sufficient.
Reading any H33 proof · the six questions

Same six answers. Different scope. The reader recognizes the machine.

  1. 1What happened?

    In 2025 an enterprise made a $4.2M credit decision, suffered a default, and filed Claim #84711. In 2031 the enterprise was dissolved through bankruptcy. In 2035 a court trustee opened the inherited litigation file and asked: "Does the chain still reconstruct?" It does.

  2. 2Who had authority?

    The dissolved root principal (princ_root_claim_…) self-signed its own dissolution as its final canonical act. Inside the substrate: a credit officer + an AI risk agent (from #15). After dissolution, no one has authority over this tenant; the chain is read-only.

  3. 3How was authority reconstructed?

    replay_until at T = June 2035 against the 11 signed canonical events (10 from #15 plus 1 EnterpriseDissolution). The engine never asks the dead tenant for help. The successor (a trustee) just reads the canonical log.

  4. 4What state was produced?

    state_id = 52a6354d74451a636682402b22503488530aebe0db28f7c6c7ae4fa740a20dbe. Verdict: Valid. The DissolutionRecord is present in the snapshot; Claim #84711 is present in the claim_events.

  5. 5What artifact was returned?

    reconstruction.json — the buyer-facing output of replay_extinct_tenant(), plus the completed ladder, plus the hero question, plus the honest-limit statement.

  6. 6How can a third party verify it?

    Run cargo test --test institutional_death_replay_001 -- --ignored against scif-backend @ 35ae26bf6. Replay at T=2035 must produce the same state_id byte-identically.

01The killer query — replay_extinct_tenant(dissolved_tenant_001)

The killer query · one line, the whole claim
asl> replay_extinct_tenant("tenant_insurance_claim_44962d9b-…")
→ buyer-facing output from one call
dissolved_tenant_id:        tenant_insurance_claim_44962d9b-25f5-5622-…
dissolved_root_principal:   princ_root_claim_44962d9b-25f5-5622-…
dissolution_id:             dissolution_insurance_claim_001
dissolution_reason:         bankruptcy
dissolution_at_ms:          1932940800000   (2031-04-01)
successor_in_interest:      court_appointed_trustee_southern_district_2031

replay_t_ms:                2064614400000   (2035-06-01, ~4 years post-death)
state_id_post_dissolution:  52a6354d74451a636682402b22503488530aebe0db28f7c6c7ae4fa740a20dbe

active grants:              2
decisions:                  2
loss events:                1
surviving claims:           ["claim_84711"]

verdict:                    Valid
category_claim:             "Evidence outlives institutions."

One query. The full chain. Four years after the company is gone. The trustee did not need H33. Did not need the vendor. Did not need the company. Did not need its employees. Did not need its systems. Just the signed canonical events and the verifier.

02The money slide

Locked Eric Beans · June 3, 2026
Evidence outlives institutions.
The company disappeared. The evidence did not.

03The honest limit a court reader must see first

The boundary · LOCKED Eric Beans

Institutional Memory ≠ Legal Truth.

The proof establishes what happened, when it happened, who was involved, under what authority, and under what policy. The proof does not establish fault, damages, legal liability, or entitlement. Those remain legal determinations made by courts, regulators, and competent counsel — not by replay engines. Institutional memory is a structural fact. Legal truth is a judgment. This proof produces the first; the second remains where it belongs.

04The scenario, in order

WhenWhat
2025Credit officer and AI risk agent approve a $4.2M loan (#15 substrate). Model + policy versions bound at decision time. Responsibility chain recorded.
2025Borrower defaults. Loss event recognized. Claim #84711 filed with the reinsurer.
2030External: litigation opens around the claim. (Not a canonical event — external narrative.)
2031EnterpriseDissolution signed by the dying root. Reason: bankruptcy. Successor: court-appointed trustee, southern district 2031.
2035The court trustee opens the file. Replays at T=2035 (four years post-death). The chain reconstructs. Claim #84711 still queryable.

05The schema (Eric LOCKED Option A — minimal)

EnterpriseDissolution {
    at_ms,                              // = dissolution_timestamp
    dissolution_id,
    dissolved_tenant_id,
    dissolved_root_principal,           // self-signs this final act
    dissolution_reason,                 // "bankruptcy" | "voluntary_wind_down"
                                        // | "regulatory_seizure"
                                        // | "merger_into_extinction"
    successor_in_interest: Option,      // None = true extinction with no successor
    signature
}

One new event kind. No continuity_id (Eric: "Not needed immediately."). No successor-recognition event (those are follow-on proofs). No additional graph complexity.

Snapshot extension: AuthorityStateSnapshot.dissolution: Option<DissolutionRecord> — skip-if-none, byte-identically backward-compatible across all 16 prior proofs.

06What this proof IS and IS NOT

This proof IS

The capstone of the H33 continuity ladder. The first proof where the dying party is the customer enterprise itself — not the vendor (that was #12) and not the vendor's own dependencies (that was #12.1). The proof a court, trustee, regulator, or post-dissolution claimant can read and understand the value of without needing to understand governance, agents, AI, blockchains, or cryptography. The institution died. The evidence survived. That is a universal concept.

This proof IS NOT

A legal verdict. A determination of liability or damages. A claim about whether a given trustee or successor is entitled to act on the dead tenant's behalf — that is a jurisdictional and legal question. A claim that all consequences post-dissolution are recoverable — only events signed before dissolution are. A reserving engine for tail liabilities. A substitute for competent counsel.

07Known limitations (Eric LOCKED — 5 total)

  1. The dead tenant cannot sign new events. That's the whole point. If litigation requires new evidence to be added (a court order, a post-dissolution settlement), the successor entity must sign on its own behalf. The dead tenant's history is read-only.
  2. Jurisdictional / legal entitlement is out of scope. The proof does not address whether a given successor IS entitled to act on the dead tenant's behalf. That's a legal question.
  3. Wind-down period quality. Replay confidence may drop in periods immediately before dissolution if event signing was rushed during operational wind-down.
  4. Phase E lock remains open as in every prior proof. L9.1 closes per-event signature verification.
  5. Institutional Memory ≠ Legal Truth. (See section 03 above. Eric: "That distinction will become important later.")

08Where this proof sits

#11
First Time Travel Replay (L5). first-time-travel-replay
proven
#12
First Independent Replay (L9, the moat — vendor dies). first-independent-replay
proven
#12.1
First Catastrophic Vendor Failure (vendor's vendors die). first-catastrophic-vendor-failure
proven
#13
First Replayable Enterprise. first-replayable-enterprise
proven
#14
First Authority Lifecycle Replay. first-authority-lifecycle-replay
proven
#14.1
First Replayable Responsibility. first-replayable-responsibility
proven
#15
First Replayable Insurance Claim. first-replayable-insurance-claim
proven
#16
First Inherited Risk Replay. first-inherited-risk-replay
proven
#184
First Institutional Death Replay — THE CAPSTONE. The customer enterprise dies; the chain reconstructs four years post-death. The 5th line of the ladder is earned.
proven now

09Evidence appendix

FieldValue
state_id at T=203552a6354d74451a636682402b22503488530aebe0db28f7c6c7ae4fa740a20dbe
Tenanttenant_insurance_claim_44962d9b-25f5-5622-bd9a-98d5580bb8a2
Tenant rootprinc_root_claim_44962d9b-25f5-5622-bd9a-98d5580bb8a2
dissolution_iddissolution_insurance_claim_001
dissolution_reasonbankruptcy
successor_in_interestcourt_appointed_trustee_southern_district_2031
T_DISSOLUTION (ms)1,932,940,800,000 — 2031-04-01
T_REPLAY (ms)2,064,614,400,000 — 2035-06-01
Years post-dissolution4
Total events11 (10 from #15 + 1 dissolution)
Surviving decisions2
Surviving loss events1
Surviving claims["claim_84711"]
Verdict at T=2035Valid
Reconstruction artifactreconstruction.json
Harnesstests/institutional_death_replay_001.rs (scif-backend @ 35ae26bf6)

10Readiness determination

Determination

First Institutional Death Replay: PROVEN IN OPERATION. The dissolved insurance-claim tenant reconstructs four years post-dissolution, byte-identically, without H33 and without the dead tenant. Claim #84711 remains queryable. The 5th line of the H33 continuity ladder is earned: Evidence survives institutions.

What this unlocks: a court trustee, regulator, R&W insurer, post-dissolution claimant, or successor litigator can now ask the deepest question that follows a corporate death — "Does the chain still reconstruct?" — and receive a deterministic, signed, byte-identically replayable answer. The continuity ladder is now complete in proven form.

What this does not unlock: legal verdicts, liability determinations, damages calculations, or entitlement questions. Institutional Memory ≠ Legal Truth.

The continuity ladder · complete

Authority survives time.

Responsibility survives authority.

Consequences survive responsibility.

Risk survives organizations.

Evidence survives institutions.

The unanswered question lives on the continuity ladder.

Issued by H33, Inc. · Eric Beans, CEO · 2026-06-03

Independently reconstructable. Inputs: scif-backend @ 35ae26bf6 · tests/institutional_death_replay_001.rs · reconstruction.json.