Lean is a language for mathematical statements and proofs that a computer can verify. This page shows one statement file from OpenAI’s release, possible paper matches and independent reports. The code-like names below identify the definitions or theorems selected by the proof-verification settings.
Seymour's second-neighborhood conjecture
Theorem selected for verification:OAI.SeymourSecondNeighborhood.exists_goodVertex
The lines of the Lean statement that state the theorem, then the definitions in the file that it uses.
theoremexists_goodVertex (r : V → V → Prop) (hr : IsOriented r) : ∃ v, GoodVertex r v := bysorry
A Lean statement states the theorem and leaves its proof as sorry on purpose. OpenAI’s proof is in a separate solution module, and a program called Comparator checks that proof against this statement.
Definitions needed to read it
Local definitions the statement names, followed through the definitions they name in turn. The match is by name in the source text, so a name reached only through notation can be missed; the full file is below.
defGoodVertex (r : V → V → Prop) (v : V) : Prop := (firstNeighbors r v).card ≤ (secondNeighbors r v).card
Possible paper match, with no recorded review
No paper statement clearly matched the Lean wording. Statement Map, the program that collects Atlas’s source records, selected this possible match using words in OpenAI’s catalogue and Lean note. No review of whether the statements mean the same thing is recorded.
Shared with the catalogue’s wording or OpenAI’s note, none of them matched in the Lean text: finite, graph, nonempty, oriented and vertex.
Theorem 1.1 of A proof of Seymour’s second-neighborhood conjecture
Theorem
Every nonempty finite oriented graph has a vertex v such that
Every nonempty finite oriented graph has a vertex \(v\) such that
\[
\abs{N_1^+(v)}\leq \abs{N_2^+(v)}.
\]
Other possible paper matches, closest wording first
Corollary 6.1 of A proof of Seymour’s second-neighborhood conjecture. Words of the Lean statement, its names split into words, that also appear in the theorem: neighbors, vertex and oriented. Shared only with the release’s name for the Lean statement or OpenAI’s note on it: directed, excluding, exactly, finite, nonempty and graph.
Corollary 5.1 of A proof of Seymour’s second-neighborhood conjecture. Words of the Lean statement, its names split into words, that also appear in the theorem: second, vertex and oriented. Shared only with the release’s name for the Lean statement or OpenAI’s note on it: two, neighborhood, graph, nonempty and finite.
Proposition 4.1 of A proof of Seymour’s second-neighborhood conjecture. Words of the Lean statement, its names split into words, that also appear in the theorem: neighbor, vertex and oriented. Shared only with the release’s name for the Lean statement or OpenAI’s note on it: finite, nonempty and graph.
Proposition 2.1 of A proof of Seymour’s second-neighborhood conjecture. Words of the Lean statement, its names split into words, that also appear in the theorem: vertex and oriented. Shared only with the release’s name for the Lean statement or OpenAI’s note on it: finite, nonempty and graph.
How Atlas selects possible matches: it compares words in the Lean statement with every statement in the family. It also splits Lean names into words. The release’s label and note receive less weight; a main theorem wins a close match. If the Lean wording yields no clear match, Atlas uses the catalogue description. This selects passages to compare; it does not establish that they mean the same thing.
Reported Comparator runs
three independent groups report that Comparator accepted runs for this Lean statement file: Carlos Toledo’s cert-machine; MathVet; Neal McBurnett’s openai-math-lean-tooling. Each group reports its own Comparator run for this statement file. Atlas has not repeated the runs.
For a configured theorem, Comparator tests whether OpenAI’s proof proves the exact Lean statement. Some files instead configure definitions for comparison by name and type. Acceptance does not establish that the statement means the same thing as the paper’s theorem.
Every Comparator challenge re-run on Linux with nanoda switched on, decided by a preregistered rule; every family’s challenge statements read against OpenAI’s headline, clause by clause. Decider: Comparator (leanprover/comparator d03acab1 = tag v4.34.0, built with the release’s toolchain v4.34.1), lean4export 076e8e57, landrun 811cfff5, nanoda_lib 3a240721 — on GitHub’s Linux runners (.github/workflows/openai-math-kernel.yml), one j…
AcceptedTheir term: “CERTIFIED”.
Re-run through Comparator with the independent nanoda kernel switched on: Lean’s kernel and nanoda both accept OpenAI’s solution.
An independent, model-assisted, pre-referee reading of each family’s challenge statements against its headline claim under a published rubric (PROTOCOL.md), with its own Comparator runs per challenge. Its protocol describes a planned error-rate study; this import does not establish that the study has been completed.
AcceptedTheir term: “comparator-sandboxed-pass”.
Re-run through Comparator in a sandboxed virtual machine: accepted.
Each challenge’s solution is built and checked by Comparator at the pinned release, on Lean leanprover/lean4:v4.34.1, recording the verdict, the check time and the peak memory; the run was still in progress at this snapshot (192 accepted, 224 pending).
AcceptedTheir term: “accepted”.
Re-run through Comparator with Lean’s kernel: accepted (the check took 123 s; peak memory 2.3 GiB).
If Comparator is run under this configuration and accepts, the solution proves the configured theorem using only the allowed axioms, and the Lean kernel accepts every step.
This configuration lists no definition holes, so every definition the statement uses is compared as it is written in this file.
Acceptance leaves open whether the Lean statement means the same thing as the paper’s theorem, whether the paper’s other claims are correct, and whether the result is new. Those questions require comparing the definitions and statements, reviewing the paper’s arguments, and reading the earlier literature.
Do family 173’s Lean statements express the advertised result?
These assessments compare all the family’s Lean statements with the whole result OpenAI describes in its catalogue. They do not assess this statement alone. Each group uses its own published rules.
MathVet and cert-machine agree on how much of the advertised result the Lean statements express.
Finds the whole advertised result stated or impliedTheir term: “full”.
The challenge statements imply the headline claim after unpacking definitions or one routine step. Their record
Their note: exists_goodVertex (r) (hr : IsOriented r) : ∃ v, GoodVertex r v over a nonempty Fintype V, with GoodVertex r v := (firstNeighbors r v).card ≤ (secondNeighbors r v).card and second neighbors {w | w ≠ v ∧ ¬ r v w ∧ ∃ u, r v u ∧ r u w} (directed distance exactly two); IsOriented = loopless + asymmetric. Exactly Seymour's conjecture.
OpenAI’s own note on what this Lean statement covers
“Seymour's second-neighborhood conjecture asserts that every nonempty finite oriented graph has a vertex with at least as many second out-neighbors as first out-neighbors. The formalized result proves this assertion, where the second neighborhood consists of vertices at directed distance exactly two. The initial vertex and first neighbors are excluded from that count, and sinks are included.”
An AI agent drafted an interpretation of that note, classifying this statement as “states a paper’s theorem as the paper does”. No human review of the draft is recorded.
Supporting material
The complete Lean statement file
40 lines, copied from release version fd4aeeb. A name defined in this file links to its line; pointing at the name shows its definition.
Declared in this fileOpenAI’s library at fd4aeebOther linked names open the current documentation for Mathlib, Lean’s mathematical library.
Links in the file: 4 to its own declarations, 7 to Mathlib’s documentation. 5 declared names also link to the same declaration in OpenAI’s library. OpenAI uses Mathlib version d13f23b. The linked documentation describes the current version, so names that have since changed may be missing there.
import Mathlib.Data.Fintype.Cardimport Mathlib.Data.Finset.Unionnamespace OAInamespace SeymourSecondNeighborhoodvariable {V : Type*}structureIsOriented (r : V → V → Prop) : Propwhereloopless : ∀ v, ¬ r v vasymmetric : ∀ {u v}, r u v → ¬ r v uvariable [Fintype V] [DecidableEq V]noncomputablesectiondeffirstNeighbors (r : V → V → Prop) (v : V) : Finset V := byclassicalexactFinset.univ.filter (r v)defsecondNeighbors (r : V → V → Prop) (v : V) : Finset V := byclassicalexactFinset.univ.filter (fun w => w ≠ v ∧ ¬ r v w ∧ ∃ u, r v u ∧ r u w)defGoodVertex (r : V → V → Prop) (v : V) : Prop := (firstNeighbors r v).card ≤ (secondNeighbors r v).cardendvariable [Nonempty V]theoremexists_goodVertex (r : V → V → Prop) (hr : IsOriented r) : ∃ v, GoodVertex r v := bysorryend SeymourSecondNeighborhoodend OAI
Every extracted statement of the accompanying papers
The statements the atlas extracted automatically from each accompanying paper’s TeX source, with links to the full sources.
A shareable summary of this page: the proposed paper match, what the Lean statement expresses, and which reviews are recorded.
Plectis Atlas
Seymour's second-neighborhood conjecture
Family 173: Seymour’s second-neighborhood conjecture
Candidate pairing
Theorem
Every nonempty finite oriented graph has a vertex v such that
\abs{N_1^+(v)}\leq \abs{N_2^+(v)}.
A proof of Seymour’s second-neighborhood conjecture
TeX label thm:main, build/source/00-introduction.tex, line 16
The Lean statement says
theoremexists_goodVertex (r : V → V → Prop) (hr : IsOriented r) : ∃ v, GoodVertex r v := bysorry
A Lean statement states the theorem and leaves its proof as sorry on purpose. OpenAI’s proof is in a separate solution module, and a program called Comparator checks that proof against this statement.
Recorded comparisons with the paper
Atlas records no contributed comparison of this statement with the paper.
Contributed Comparator run reports
Atlas records no contributed report of running Comparator for this statement file.