Home·The theorem·The proof in one reading·Architecture·Units·Manuscript·Glossary·FAQ·Work items·Data·Method·Provenance·Changes

How the manuscript is written

Contents

1. What is being written, and against what 1

2. Why a process at all 2

3. Statements first: the spine 2

4. Style rules (binding, partly enforced by a program) 3

5. Who does what 3

6. The cycle for each section 4

7. Automatic checks 5

8. Records 5

9. What this has caught so far 6

10. What the process does and does not establish 6

Changes to this process 7

This page describes, in detail, how the manuscript is being written: who does what, what is checked, by whom, against what, and what the checks do and do not establish. The process is still in use and is revised when it fails; the changes are recorded at the end.

1. What is being written, and against what

The manuscript gives a complete natural-language proof of the result formalized in OpenAI's Lean proof of the construction of four-dimensional quantum Yang–Mills theory, at the fixed commit 3456e5e. It has two parts:

The authority is the Lean. The manuscript claims nothing the Lean does not prove. A statement may be weaker than its Lean counterpart, or stated in a more natural form, but never stronger. "The Lean" means the declarations that the main theorem actually depends on, as computed from the compiled files (about 74,000 declarations; see the method). The source also contains alternative routes that the main theorem does not use; these are not evidence for anything in the manuscript.

The rest of this repository (the summary, the unit outlines, the dependency graph) serves as a map for finding things in the Lean. It is never cited as evidence.

2. Why a process at all

The obvious approach is to ask a capable model to write the paper from the Lean. We tried that, and it failed in ways that are easy to miss:

The process below is built against these failure modes. Much of it comes from an earlier project of the same kind, a paper written from a completed Lean proof, where the same failures occurred.

3. Statements first: the spine

Before any prose is written, every statement of Part I is fixed in a single document, the spine:

Each statement is written in natural form: one result per statement, quantifiers first, conclusion displayed. The objects it uses are set up in the text before it, and side conditions of the formal version go to Part II lemmas. A clause map then checks that nothing was lost: every clause of the Lean's main statements is assigned to a statement of the spine, and the union of the natural statements must equal what the Lean proves.

Freezing. The project lead approves the spine, after which the principal statements and the main theorems are frozen. A frozen statement can change only through the drift protocol: the old text, the new text and the reason go to the project lead, and nothing changes without approval. Part II lemmas are not frozen. They can be split, added or reworded as the proofs are written, and every such change is recorded in a drift log.

4. Style rules (binding, partly enforced by a program)

rule limit
statement (theorem, proposition, lemma) target 100 words, hard cap 150
definition target 120 words, hard cap 200
ideas per statement one
"there exists a family such that the following assertions hold" never: the conditions go in the setup
definitions concrete, by formula, with one sentence of purpose; never a translation of a Lean structure
Part II about one numbered lemma per page; a proof longer than three pages is split at a genuine intermediate statement
standard results cited exactly: name, hypotheses, numbering, checked against the source
Lean names, file paths, process vocabulary never in the text
references between numbered items always by cross-reference, never by a typed number

The exposition follows the presentation of the renormalization group in the work of Bauerschmidt, Brydges and Slade, in this order: the objects, the inductive step, the multiscale theorem, the continuum results, the deduction of the main theorem, the constructions.

5. Who does what

role who does
project lead a person sets the goals, approves the spine and every change to a frozen statement, reads each finished part and sets the level of detail and length
editor an AI model (Claude) writes the tasks, integrates proposals into the manuscript (the only one who edits it), runs the checks, keeps the records, decides on findings
writers AI models (GPT-6.1 Sol, high or extra-high reasoning effort) write proposals for one section at a time, in a separate directory; never edit the manuscript
reviewers AI models (Claude Opus), each in a fresh context read a frozen snapshot and report; never edit anything

The separation is deliberate. Writers propose and the editor integrates, so that one reader sees the whole manuscript and its notation stays consistent. Reviewers have no access to the writer's reasoning, only to the text, the spine and the Lean, so they cannot inherit its mistakes.

6. The cycle for each section

  1. Task. The editor writes the task: what the section must contain (its statements from the spine), its sources, its page allowance and the rules above. Over the allowance means not done.

  2. Proposal. A writer drafts the section in its own directory. Alongside the text it delivers a table pairing each statement with the Lean declarations it rests on, notes recording what it could not do and its least certain sentence, and the results of its own checks.

  3. Integration. The editor reads the proposal in context, integrates it into the manuscript, compiles, and runs the automatic checks.

  4. Frozen snapshot. The section, everything before it, the spine and the style rules are copied into a snapshot with a manifest of SHA-256 hashes. A review verdict applies to that snapshot only.

  5. Independent reviews, each by a separate reviewer:

  6. Response table. Every finding gets a row: the finding, the decision (applied, or declined with a mathematical reason), the exact edit, and how it was checked. Findings are never deleted or rewritten. The fixes are made by a writer as a new proposal and integrated by the editor.

  7. Re-check. The same reviewers check the new version against their own earlier findings and mark each one resolved or not resolved. They also check the reasons given for declining findings, and report anything the fixes broke.

  8. Delivery review. A last reviewer checks:

    It looks at every rendered page and states what its review does not establish.

  9. The project lead reads it. Comments on level and length become binding style rules for the sections not yet written.

Part II starts with two pilot sections, one on the ultraviolet side (§12, path actions and the coupling reset) and one on the infrared side (§15, infinite volume). They go through the whole cycle and are read by the project lead before the other eight sections are written. Each later section then follows the same cycle.

7. Automatic checks

Run after every integration:

Passing these checks means none of these mechanical faults is present. It says nothing about whether the mathematics is right.

8. Records

The working records (tasks, review reports, response tables, the statement register) are kept in a separate working repository.

9. What this has caught so far

Examples from the first rounds. None of them would have been caught by compiling the text:

10. What the process does and does not establish

Changes to this process