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

How the map was made

Contents

Source compilation and kernel checking 1

1. The dependency graph 2

2. Coarse-graining 3

3. Key statements 3

Statement and explanation checks 3

5. The unit outlines and the summary 4

Unit outline status 4

Published evidence and tools 4

This page separates checking the formal proof, interpreting its statement, extracting declaration references and reviewing the explanations. The source is fixed at commit 3456e5e75cf8d4cd558955a5c7638fba2d68f464. The FAQ evidence table gives the scope of each check.

Source compilation and kernel checking

The released source uses Lean 4.32.0 and pinned external libraries. Its verification log records a type comparison for YangMills.jointExistence, an axiom check for seventeen named results, and a successful kernel replay of 100,168 project declarations reachable from those results. It reports only propext, Classical.choice and Quot.sound as endpoint axioms. The checking program compares the solution with a separately loaded reference and replays project declarations with only external libraries initially present.

These are checks of formal declarations and proof terms. They do not establish that an English statement expresses the intended physics, that an outline explains every estimate, or that the mass-gap problem has been solved. The placeholder in the reference Challenge.lean is separate from the solution's imports; the source's verification account explains this distinction.

To rebuild the project from source, use a fresh checkout without the precompiled project archive. The following follows the source verification instructions; it downloads compiled dependencies, compiles the project and runs the separate checks:

git clone https://github.com/yang-mills-group/OpenAI-YM-20261028
cd OpenAI-YM-20261028
git checkout 3456e5e75cf8d4cd558955a5c7638fba2d68f464
lake exe cache get
lake build WilsonReference WilsonConstruction
lake env lean -j1 -DmaxHeartbeats=0 -DmaxRecDepth=4096 VerifyJoint.lean
lake env lean -j1 -DmaxHeartbeats=0 verification/Usage.lean
lake env lean -j1 verification/CompactCheck.lean

The build targets are specified in the pinned Lake file. Expected messages from VerifyJoint.lean include TYPE_MATCH, ENDPOINT_AXIOMS and REPLAY_PASS; inspect the complete output and exit status. This recipe still trusts the downloaded external libraries. The separate compiled project release is convenient for exploring the proof, but loading it and finding all build targets up to date does not independently recompile the project. A checksum checks the downloaded archive against its published digest.

1. The dependency graph

2. Coarse-graining

The declaration graph is reduced in four steps. Inclusion in the unit assignment table should not itself be read as a claim of reachability from YangMills.jointExistence.

  1. Ownership. Within a chosen set of roots, helpers reached only through one result are folded into that result, using the dominator tree.

  2. Scales. A result is retained at scale M when its proof and folded helpers occupy at least M lines. Scales from 100 to 3,200 lines give increasingly coarse views.

  3. Shared material. Material used by many results is grouped by source folders and similarity of use, much of it in the renormalization-group estimates.

  4. Units. Groups are cut and merged into thirty-two mathematically coherent units. A unit's declaration allocation and its explanatory subject can differ. The assignment table records allocation; the unit index describes the questions the outlines address. References between units can occur in both directions because each unit contains several declarations; this does not imply a circular formal proof.

3. Key statements

Statement and explanation checks

The statement page transcribes the public theorem, its definitions, quantifiers and qualifications against the pinned Lean. The extra conclusions D1–D16 have a different scope: as that page records, D3 and D5–D15 are summarized from definitions and comments and were not all unfolded to the last definition. This comparison is an AI-assisted interpretation of formal text, separate from a kernel check and from an independent mathematical reading of the proof.

The glossary was written from definitions, fields and uses. Its certain, probable and tentative labels describe the strength of that interpretation. They are not unit review statuses or certificates of mathematical correctness. The architecture and work-item descriptions likewise need to be read with their linked sources and qualifications.

5. The unit outlines and the summary

Unit outline status

Each outline has a place in a three-round review. All outlines are published; the index gives their current statuses.

Status Review described by the label Limit
Draft Claude Sonnet writes propositions, hypotheses, strategy and proof sketches from the source and key statements. The explanation has not completed the next two reviews.
Checked Claude Opus compares numbered statements with the linked Lean, including hypotheses and quantifiers, reads the main proof steps, and corrects and rewrites the account. Subsidiary estimates may remain at statement level; see the unit's “What remains unexplained” section.
Edited A GPT model makes a further comparison with the Lean and edits the exposition. This is not a complete independent human proof review; local limitations still apply.

The second round found dropped hypotheses and overbroad statements in the first two units. It also found that the coupling's one-loop coefficient is computed in the proof, where the draft had described it as assumed. The labels record review of exposition; a draft outline does not mean the linked formal result is unproved.

The summary was written from the outlines by a GPT model and edited by Claude Opus. It is revised as the outlines improve. Human mathematical judgment remains needed to assess whether these explanations give a satisfactory account of the construction; the manuscript being written in public is under construction.

Published evidence and tools

The data directory contains the published unit, declaration-assignment and key-statement tables. The source's verification programs and logs linked above are available at the fixed commit. The separate programs used here to extract and group the graph and select statements were tested on the earlier Navier–Stokes formalization; they have been announced for publication but are not yet included in this repository. References to unpublished working analyses are not reproducible evidence for readers.

Report a correction with the page, heading, quoted sentence and proposed correction or pinned Lean reference.