Field noteNov 5, 20266 min read1 source

The Stacks Project, formalized in Lean

In one minute

Axiom says it has released a Lean formalization of the entire Stacks Project, a roughly 7,500-page reference for modern algebraic geometry. The result is described as a single machine-checked library of about 16 million lines, intended to give researchers and AI agents reusable verified foundations for future proofs.

What changed: Axiom released a Lean formalization of the entire Stacks Project: about 16 million lines in one reusable, machine-checked library for modern algebraic geometry.

What happened

On November 4, 2026, Axiom announced a Lean formalization of the Stacks Project. The original open-source reference, initiated by Columbia University mathematician Johan de Jong in 2005, has grown through contributions from hundreds of mathematicians over two decades. Axiom describes it as roughly 7,500 pages of foundational material for modern algebraic geometry. The formalization spans some 16 million lines of code and is presented as the largest integrated, reusable library of formalized mathematics built to date.

The release makes the mathematical development available as a single machine-checked library. Researchers and AI agents can import definitions and theorems into new formal proofs. Axiom says permanent Stacks tags connect Lean declarations back to the canonical text. At stacks.axiommath.ai, readers can view the original pages alongside corresponding Lean code and explore an interactive dependency graph. A source tag can map to multiple formal definitions and lemmas, so the relation is not necessarily one tag to one declaration.

Axiom’s explanation centers on reuse. Algebraic geometry proofs can depend on long chains of results from areas such as commutative algebra, schemes, sheaves, cohomology and algebraic stacks. The company argues that, until now, the mathematical material existed in the Stacks Project but corresponding Lean infrastructure did not. A formalized foundation lets a new proof reuse prior definitions and results rather than rebuild that machinery; Lean’s kernel checks that a cited result is applied with its hypotheses satisfied.

The company says producing a codebase at this scale required coordinated AI-agent swarms to translate, prove and integrate thousands of theorems in parallel. It emphasizes that this was also a software-engineering task: a large verified development needs abstractions, stable interfaces and components that work together, rather than many isolated generated scripts. The release builds on Lean and Mathlib foundations and years of work by their communities. The supplied announcement does not specify a price or access restriction; it points to the public project interface for browsing the material.

Axiom contrasts this release with its October 27, 2026 formalization of the Classification of Finite Simple Groups. That work is organized around a single landmark theorem, while the Stacks Project is described as a foundational library of interlocking definitions, constructions and lemmas, intended for reuse across future proofs. The stated aim is to establish a starting point for work in algebraic geometry and neighboring fields, not to announce a particular new theorem or an AI system that can independently do mathematics.

What the archive adds

Our earlier coverage of Anthropic’s formal-math repository described formalized complexity results such as 3SUM and APSP. Axiom’s announcement is a new fact on the broader formal-mathematics story: it concerns a much larger, connected library for algebraic geometry, built for reuse rather than a set of focused formalizations. The overlap is formal proof infrastructure, not a shared project.

Trend signal

This supports scientific agents need artifact evidence: progress is more useful when another researcher can inspect and reuse a verifiable artifact. Axiom points to machine-checked declarations, permanent links back to the source text and an interactive dependency graph. The announcement is a vendor account, however; it does not independently establish the library’s completeness or how readily outside researchers can extend it.

Why now

Axiom frames the release against a practical mismatch: AI systems can generate mathematical arguments faster than people can inspect them by hand, while modern algebraic geometry has lacked comparable Lean infrastructure. The announcement also follows the company’s October 27 formalization of the Classification of Finite Simple Groups, positioning this library as a different kind of formalization—broad reusable foundations rather than one central theorem.

Connections to other events

The archive’s earlier Anthropic formal-math note concerns machine-checked mathematics, but Axiom’s project is not an extension of Anthropic’s repository. The source itself also connects the release to Axiom’s recent Classification of Finite Simple Groups formalization, explicitly distinguishing its single-theorem focus from the Stacks Project’s interconnected library. Both illustrate different engineering shapes for large formalization efforts.

Why it matters

For teams building mathematical agents, the important distinction is between producing plausible proof text and producing work that can be checked against a trusted formal system. A large reusable library potentially changes the amount of foundational work an agent or researcher must repeat: a proof about curves can call on formalized results about schemes or cohomology instead of starting those foundations from scratch. Stable tags and explicit dependencies also give people a route from code back to the source mathematics, which matters for review and correction.

The broader engineering lesson is similarly concrete. Scaling verified work is not just a matter of asking more agents to generate code. Their outputs need interfaces, abstractions and integration into a coherent project, with a checker enforcing correctness at the formal boundary. For AI builders, the announcement is evidence of an ambitious architecture and workflow, not yet evidence that agents can reliably discover new mathematics without expert supervision. The library is most valuable if others can inspect, cite and extend it in real proofs.

Limits and uncertainty

These claims come from Axiom’s own announcement. The supplied material does not independently verify the 16-million-line count, the “largest” characterization, completeness of the formalization, or the quality and maintainability of every component. It gives no external evaluation, adoption figures, examples of an independent research result built on the release, or comparison of human and agent contributions. It also does not quantify the time or compute involved, state licensing or contribution terms, or explain whether every part is equally accessible to users. The announcement says AI agents helped with translation, proving and integration, but does not establish how much work they completed autonomously or how humans reviewed it.

Skill to build now

For a formal-proof project, practice tracing a theorem across its provenance and dependency chain. Pick one result in the Stacks Project, locate its permanent source tag, then inspect the corresponding Lean declarations and their prerequisites in the project browser. This is a concrete way to evaluate whether a formal library is usable for your task: can you find the theorem, understand its assumptions and identify what your own proof would need to import? Do not treat a generated proof as reusable until the checker and dependencies are inspectable.

Reader takeaway

Axiom’s release is notable because it aims to turn a major mathematical reference into one connected, machine-checked foundation that future proofs can reuse. The practical test is not the headline scale alone. It is whether researchers and agents can navigate its dependencies, verify its claims and build new work on top of it.

Evidence / sources

  1. 1axiommath.ai/research/the-stacks-project-formalized
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAnthropicExplore the anthropic topic hub.
  2. 02archiveField NotesOpen the latest editorial analysis.
  3. 03sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract