When we say "the evidence remains," we mean something specific. Not abstract proof. Not a 74-byte primitive. The actual operational history of an organization: every approval, every transfer, every compliance check, every governance vote, every AI decision, every authorization, every override, every audit finding.
Each of those concrete events produces a proof at the moment it happens. The collection of those proofs is the operational history. That history survives changes in the chain, the vendor, the database, and the system that produced it.
Evidence means the history of what happened.
Concretely: every approval, every transfer, every compliance determination, every AI decision, every governance action. Each one is a single proof. The collection is the operational history. The history outlives the infrastructure that produced it.
Four concrete examples
Tokenized Fund
5 years of operating a private credit fund on a chain that is now being abandoned
2.04M
transfer authorizations
40,180
compliance determinations
What survives the chain abandonment: every one of these events. The fund re-issues its token on a new chain. The new chain anchors a single batched commitment over the entire historical evidence corpus. Auditors verify every prior approval, transfer, and compliance check exactly as before. The fund did not have to reconstruct anything.
Bank AI Compliance
A bank's internal AI fraud system produces millions of decisions per quarter
3.2M
transaction approvals
94,300
human override events
22,400
model version updates
What survives the AI vendor change: every decision the previous model made remains independently verifiable. When a regulator asks "what did your model determine about transaction X in 2027 under what policy?" — the bank answers with the original proof, not a reconstruction. The bank switches AI providers without losing the audit trail that the previous provider's decisions produced.
Regulated Insurer
An insurer's claims operations across three product lines for seven years
340K
underwriting decisions
186K
reinsurance determinations
52
policy framework changes
What survives the core system migration: every claim decision, every underwriting determination, every reinsurance allocation. When the insurer migrates from one core insurance system to another, the historical record does not move with the system. It exists independently as PQ-signed proofs. The new system inherits zero operational history and zero audit risk.
Government Records
A government identity registry operating across three database generations and two vendor changes
3.8M
document attestations
410K
cross-border verifications
85K
administrative overrides
What survives the database and vendor changes: every issuance, every revocation, every administrative override. A citizen whose identity was issued in 2023 under one vendor's database can have that issuance independently verified in 2035 under a different vendor's database. The continuity of the record is decoupled from the continuity of any specific operator.
What does NOT survive
Honesty about this matters as much as the survival claim itself. H33-74 does not preserve everything. It preserves the operational history. It does not preserve:
The asset
Tokens, funds, identities, and other on-chain assets are reissued on the new chain as normal tokenization work. The proof of every prior approval that touched the asset survives; the asset itself is reissued.
The system
Applications, databases, core systems are replaced as normal IT lifecycle work. The proof of every decision the old system made survives; the old system is decommissioned.
The vendor
SaaS providers, AI providers, custody providers may change. The proof of every action under the old vendor survives; the new vendor inherits operational history without operational dependency.
The chain
The notarization chain can be replaced. The proof of every event the chain anchored survives; the chain anchor is added on the new chain.
What survives is the answer to the question: what happened, when, under what authority, with what input, with what outcome?
Why this matters at the executive level
Every system runs on a five-to-ten-year operational horizon. Within that horizon, the underlying infrastructure changes: vendor turnover, cloud strategy shifts, database transitions, chain selection updates, AI provider changes. The cost of those transitions is usually not the new infrastructure — it is the loss of operational history that the old infrastructure was holding hostage.
H33-74 separates the two. The infrastructure can change on its normal schedule. The operational history does not have to move with it.
When a CFO asks "if we change chains, how much audit history are we going to lose?" — the answer is zero. When a CISO asks "if our AI provider changes models, can we still answer regulator questions about decisions the old model made?" — the answer is yes. When an auditor asks "can you produce the original approval evidence for transaction X from four years ago when your treasury system was a different product?" — the answer is yes.
Operational history is the asset that compounds. Five years of approvals, decisions, and compliance determinations are usually worth more than the systems that produced them. Most organizations lose that history every time they change infrastructure. H33-74 makes the history independent of the infrastructure.
Related