00
The Ledger
The single place CTinFold declares, once and permanently, that something real happened. The foundation every other component in this system exists downstream of.
The single source of truthOpen component →
01
The Payment Registry
A relation that opens a series of payments and runs, provably, to zero. How partial settlements stay sealed across time.
Payment mechanismOpen component →
02
The Topology
How a declaration becomes proof. The chain from verdict to seal to three independent locations that must share one hash.
Proof architectureOpen component →
03
The Deposit Registry
Deposits and withdrawals under one registry, with a balance that is computed from sealed events, never stored. Active until zero, then settled.
Deposit mechanismOpen component →
04
The Relation Registry
What the system will seal, and what it will not. Twenty-nine allowed relations, six forbidden, and the reason the boundary is one of proof.
Relations & policyOpen component →
05
SCFP
Smart Categories and Folding Press. The export layer. Four categories of document, the thirty-three statements, and the export hash that proves each one.
Export & deliveryOpen component →
06
Failure Artifacts & UniCat
Two systems that make CTinFold trustworthy by design. Every failure leaves a permanent trace, and every document is read through one governed dictionary of relations.
Integrity by designOpen component →
07
The Resurrection Property
A rehearsed total loss, restored byte for byte from sealed artifacts, and a single forged character refused. How CTinFold proves its own continuity.
Continuity by proofOpen component →
08
The Category Registry
A category is a registration, not a text field. How CTinFold forces the current category forward until the partner deliberately replaces it, and binds tax to it as one unit.
Registry mechanismOpen component →