Lab › Proof Atlas: Compiled Proofs › Findings

Proof Atlas: Compiled Proof Graphs and Article Coverage

Complete compiled proof graphs from two Lean corpora, their shared structure, and the limits of correspondence with a mathematical article.

By Igor Moiseev · 11 October 2026
Proof Atlas: Compiled Proofs
  1. Proof Atlas: Compiled Proof Graphs and Article Coverage ← you are here

Measured result · 12 October 2026. Proof Atlas represents every owned declaration in two finite Lean corpora, including complete compiled theorem bodies and local dependency links. This establishes structural coverage of the extracted formal objects. It does not establish complete formalization of the accompanying article or automatic discovery of its mathematical argument.

Read the article with synchronized proof views · Coverage and evidence

Lean checks a proof term against a proposition. In a context of assumptions $\Gamma$,

\[\Gamma \vdash p : T\]

means that the term $p$ has type $T$. An exact structural representation must retain expression children, declaration references and variable binding. A drawing’s layout is an additional choice, not a mathematical invariant of the proof.

Complete compiled proof inventories

The extracted inventory includes every owned declaration in two separately identified snapshots:

Extracted corpus Modules Declarations Theorems Available bodies Shared expression nodes Expanded occurrences
Published snapshot 15 739 561 715 549,509 49,693,046
Working snapshot 26 1,359 1,083 1,335 1,277,896 670,018,056

Both inventories include complete types, available bodies, eight recursor reduction rules and exact local declaration references. External library references remain named boundaries. The published and working snapshots are different corpora; their counts must not be combined as independent samples.

Structural sharing. The working corpus’s 670,018,056 expanded occurrences are represented by 1,277,896 shared nodes. Sharing retains binder names, annotations and typed metadata. It does not identify proofs up to mathematical equivalence. A bound variable’s meaning follows its root-to-node path: a shared node may occur under several different enclosing binders.

The private native check kernel-checked all extracted types, available bodies and reduction rules and compared inferred types. Public packet audits reproduce graph, scope, hash and inventory checks. Original source projects and tactic scripts remain private, so these public audits are not an independent project-source kernel rebuild. The coverage report links the exact inventories and checks.

A worked crossing proof

The first measured object is CrossingData.crossing, a counting lemma in the $\mathrm{SE}(2)$ formalization. Its exported type and proof contain:

Measured quantity Value
Expression occurrences 7,288
Structural child edges 7,286
Bound-variable-to-binder links 431
Constant-use occurrences 2,892
Distinct directly referenced declarations 42
Maximum expression depth 49

The type has 203 occurrences and the proof 7,085. The complete term payloads retain declaration names and occurrence paths. For example, occurrence 1852 has 105 occurrences and decodes to C.branch σ p = ψ + (2 : Real) * C.K * (↑n : Real). It is an equality proposition; selecting it does not itself supply a proof of that equality.

A declaration reference reveals its supporting argument only when that declaration’s body is included. Repeated syntax is not by itself mathematical redundancy or proof equivalence.

What the article correspondence establishes

The web article preserves the published mathematical manuscript. Its Lean comparison audits all nine numbered statements, using 49 declaration headers and 107 original statement lines:

Article coverage Audited result
Numbered statements Five partial, conditional counterparts; four unformalized
Proof blocks Five of six link to complete supporting compiled proofs
Floquet proof Unformalized in the published snapshot

Complete declaration coverage is not complete article formalization. The checked scalar counting clauses retain finite-tangency assumptions (hfin, hL/hR). They do not establish all the article’s claims about first-root continuity and extrema, quartic zero order, Floquet asymptotics, late folds or separatrix limits. The statement-by-statement review records the exact boundaries.

Article links are curated correspondences with source hashes, labels and expression paths. Several expressions can inherit the same enclosing passage; a small kernel node need not have an individual article sentence. The links record provenance. They do not certify equivalence between prose and Lean.

Structure does not yet explain the proof

For the crossing lemma, exists_branch and unique_branch expose the mathematical mechanism:

\[\underbrace{\text{continuity + endpoint coverage}}_{\text{existence}} \quad + \quad \underbrace{\text{monotonicity + endpoint identification}}_{\text{uniqueness}} \quad\Longrightarrow\quad \text{exactly one crossing}.\]

Intermediate-value reasoning supplies existence. Strict branch monotonicity and identification of glued endpoints supply uniqueness. A degree-one winding argument alone would not prove injectivity. The compiled library contains both supporting proofs, but this concept map is still a human interpretation anchored to them.

Not established: that graph clusters isolate mathematical ideas, that repeated subtrees admit certified semantic compression, or that the diagrams improve reader comprehension. No reader-comparison result or automatic explanation result is reported.

The kernel and source language also remain distinct. The pinned Lean 4.33.1 reference covers all 12 Expr, 6 Level and 4 Syntax constructors. Surface terms, tactics, commands, macros and elaborator structures are curated families, not an exhaustive inventory of Lean extensions. A final compiled term does not recover the original tactic script or source-to-term trace. The language reference and methodology record document that scope.

References and nearby work