The Resurrection Property.
Restore from proof, not from hope.
Every financial system claims to have backups. Almost none can prove that its backups are the system. On 02 July 2026, CTinFold was subjected to a rehearsed total loss and a deliberate forgery. This is the record of both claims and the numbers that prove them.
A backup is a promise. A resurrection is a proof. Ordinary systems keep copies of their data and assume the copies are faithful and complete, and the assumption is tested for the first time on the day of the real loss. CTinFold does not rely on that assumption, because the system does not merely have artifacts, it runs on them. Every balance, every statement, every state is derived from sealed events on disk. On 02 July 2026 a total loss was rehearsed. The full artifact set was restored to a foreign location and independently re-sealed, and the reborn seal matched the golden seal byte for byte across 53,404 files. A second restore was then deliberately forged, a single character injected into the ledger, and the seal diverged from it instantly. Two claims, Resurrection and Refusal, both held and both on the record.
A backup is a promise. A resurrection is a proof.
A copy kept and never tested is a promise, not a proof. A backup shows that files survived. A backup verified with a hash shows that the copy is exact. Only a rehearsal shows that a system built on those files can be restored and continue to operate correctly.
A system that runs on its artifacts.
CTinFold can be rehearsed against total loss because nothing in it is stored as an opinion. Balances are arithmetic over sealed events. Statements are derived. State is recomputed on every restart. A system whose truth lives entirely on disk can be restored entirely from disk. Every action is determined before it runs, by rule, not by discretion. That determinism is also what makes restoration verifiable rather than assumed.
The seal. One number for every byte.
The sealing method has two floors. On the first floor, every file is fingerprinted with SHA-256. On the second floor, all the fingerprints are written into one manifest, sorted by path so the order is always identical, and the manifest itself is fingerprinted once. One number stands for every byte of every file. Same input, same seal, forever, on any machine. Change one character anywhere, and the summit changes.
Claim one. Resurrection.
The golden copy was restored in full to a fresh, foreign location, simulating a machine that had lost everything. The reborn copy was then independently re-manifested and re-sealed by the same method, with both steps rebuilt from zero and no reference to the original seal during computation.
Identical, byte for byte, across all 53,404 files. The restored copy satisfies the requirement that the full artifact set remain reloadable after a total loss of location.
Claim two. Refusal.
A second full restore was made to a separate foreign location. A single character was then appended to the ledger file, and the copy was re-manifested and re-sealed by the same method.
The altered seal diverged from the golden seal immediately. The change to one character in one file changed that file's hash, which changed its line in the manifest, which changed the master seal. Verification did not require inspecting the file set by hand. Comparing two seals was sufficient to detect the alteration.
The record, as examined.
During the first sealing attempt, two files whose names contained bracket characters were silently skipped by a defect in the hashing command. The resulting seal was declared invalid and discarded, because a seal missing even two files is not a seal. The command was corrected to literal path handling, and the entire set was re-sealed cleanly. The failure surfaced, was recorded, and was corrected before the examination was accepted. Nothing about the examination's own tooling was assumed to be correct without a check.
Any alteration to a sealed file is mathematically detectable, because it changes the file's hash, which changes the manifest, which changes the master seal. This is what the two claims above establish. It was already lost once. On purpose. It came back identical. Here are the hashes, twice.
SHA-256
Blank this value and recompute
SHA-256 of this page to verify it is untouched.