SCFP.
Delivering what was proven, not what was entered.
SCFP is the export and proof delivery layer of CTinFold. Once declarations are sealed and the statements are produced, SCFP organizes them, sorts them into four categories, and delivers them as documents. Every document it produces traces back to a sealed event, and carries an export hash that lets anyone confirm it is untouched.
A partner using CTinFold does not compile reports at year end. They declare events as they happen, the system seals each one, and the statements are produced continuously from what was sealed. SCFP, Smart Categories and Folding Press, is what turns that sealed material into documents a partner can hand to an auditor, a regulator, or a board. It delivers what was proven, not what was entered. Every document belongs to one of four categories, and every exportable document carries an export hash computed from its content at the moment of export. The proof chain runs from the declaration, to the statement, to the document, end to end.
Delivered, not compiled.
In the ordinary world, financial statements are assembled. Someone gathers entries, reconciles them, and produces a report at the end of a period. The report is a summary of records, and it is only as trustworthy as the hands that assembled it. CTinFold inverts this. The partner declares events. The system seals them. The statements are produced from what was sealed, continuously, and SCFP delivers them on demand.
Four categories of document.
Everything SCFP produces belongs to one of four categories. Three are sealed documents that carry an export hash. The fourth is a live view that is deliberately not exportable, because it is a state, not a document.
The primary proof documents. Verdict, topology proof, and ledger entry for a single declaration. A partner presents Category A to an auditor as evidence that a specific transaction was sealed.
What a traditional audit would examine, produced from what the topology proved rather than from manual entries. Financial, accounting, tax, and nine control statements.
Open claims and their status, a summary of failure artifacts, and the full financial year in one sealed document. For year-end close and board reporting.
Real-time topology status, live declaration feed, pending items, payment registry state. Not exportable, because it is a live state and not a sealed document. Sealed documents are A, B, and C only.
The thirty-three statements.
Per partner, per financial period, the independent verifier produces thirty-three statements. It reads its own copy of what was accepted and never reads the ledger, so the statements are independently derived. They fall into four types.
The sealed record of every accepted declaration, written once and never changed.
Thirty-three statements per partner per period, derived from its own copy, never from the ledger.
Every document carries its own proof. The export hash.
Every PDF in Categories A, B, and C carries an export hash in its footer, a SHA-256 computed from the document content at the moment of export. It does not replace the topology hash. It extends the proof chain to the document itself. The topology hash proves the declaration was sealed. The export hash proves the document delivered is the same document the system produced. Two proofs, neither replacing the other.
The result, for a partner, is simple to state. They do not compile. The system delivers. At any point in the year they can export proof that a specific transaction was sealed, their current period statements, or their cycle summary. Each is a PDF with an export hash. End to end. Sealed.
SHA-256
Recompute to verify
this document is untouched.