Formally verify the Stacks Project in Lean with a fleet of agents

Axiom Math ran parallel AI agents that turned the Stacks Project's roughly 7,654 pages of algebraic geometry into about 16 million lines of machine-checked Lean.

Done withCustom agent· Nov 5, 2026

What they did

Axiom Math, a startup led by CEO Carina Hong, set its own fleet of AI agents on the Stacks Project, the open-source algebraic geometry reference that Columbia mathematician Johan de Jong started in 2005. The job was to translate every definition and theorem into Lean code that a proof assistant checks line by line, while keeping the dependencies between results intact. The team imposed a loose hierarchy rather than assigning each agent its work: according to Ashvin Swaminathan of Axiom's technical staff, the agents found tasks for themselves and picked out pieces they could work on in parallel. Axiom used models it trained in-house for mathematics, and an internal Lean expert guided the agents early on.

How it went

Axiom announced on 4 November 2026 that the whole library, about 7,654 pages, is now formalized as roughly 16 million lines of checked Lean. Hong told TechCrunch the team had not been sure the agents could keep that many interconnected results consistent. Swaminathan says it fills the largest gap in formalized mathematics, since algebraic geometry had little Lean coverage before.

Worth knowing

This is a company announcement reported by TechCrunch, not an independent audit; the article gives no cost, run time or count of agents. The agents and the models behind them are Axiom's own and are not available to the public. The result is the formal library, which other researchers and agents can now build on.

Try it

With Custom agent· 3 parts to fill in

Formalize [chapter or section of a mathematics text] in [Lean 4 with Mathlib]. First list every definition and result in it with the earlier results each one depends on, and check which already exist in [the library]. Then work through them in dependency order, writing each statement and proof as code and running the proof checker after every file. Keep names and statements faithful to the source; do not weaken a theorem to make it compile. Leave anything you cannot prove marked with sorry and a note. Stop when the section builds with no errors and give me the list of remaining sorries.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related