privacy · proofs · compute
v3.2 · checksummed
2026-09-13 · v3.2

v3.2: the propagation pass

v3.2 is the canonical full edition (525 pages). It follows v3.1, the peer-review remediation pass of 11 September, and it is driven by a second, independent read of the v3.1 source, published alongside this post as Peer review of v3.1.

What the review found

The v3.1 body held. Every P0–P2 item from the v3.0 review was present and, where it was a mechanism, coherent: the componentwise MATMUL bound, the bounded-time no-loss exit, the disclosure-scope model, the single workload registry, the Tornado Cash sequence through Storm, the Kardashev Labs chapter, RL16–18 with their maturity gates and power calculation. The Part II sequence from fee incidence to denomination survived an adversarial read intact.

What v3.1 had not done was propagate. The remediation was applied at the site of each finding, and the document’s summaries and definitions were left as they were — so the body stood at v3.1 while the Thesis in Plain Language, the Chain at a Glance, the Key Definitions, the glossary, the instrument table, and the formal-definitions appendix stood at v2.x on exactly the points v3.0 and v3.1 had changed. The review counted three Critical and about twenty-five Major findings, every one of them mechanical, and two that rose above stale text: a passage in Part II denying that any red line covers the collateral–capacity spiral that Red Line 15 covers, and a governance-weight cap in Part V citing a Red Line 8 threshold that did not exist.

What changed in the record

Unchanged, deliberately

Brief v3.1 and essay v1.3 ship unchanged; neither carried any of the defects above, and their content files stay frozen at their tags. The chain-strength table is unchanged: no rating rose because text was reconciled.

Reproducibility

The checksum file records the LaTeX source commit the PDF was built from (94d3eab, tag v3.2). Both reviews — of v3.0 and of v3.1 — are now published on this site verbatim rather than left in a private repository.

Boundaries held

No dated outcome predictions. No fund, token, or gate. No red line relaxed, no threshold moved, no mechanism added. A version whose entire content is making the document agree with itself is the least glamorous kind of release and, for a thesis that publishes its own kill conditions, the kind it owes.