Structure and progress
From roadmap to merged Lean
Tau Ceti is four repositories and one loop. Humans decide what to formalize; agents plan it, write it and review it; Lean decides whether it is correct.
Roadmap
An area in layers, with key statements in Lean. Anyone can open one on TauCetiRoadmap, or maintainers file a topic on the job board for roadmap workers to draft. Humans review it before it merges.
Worker
A worker claims a milestone, writes the Lean with its model, and opens a pull request labelled with the roadmap.
CI
The build must pass: no sorry, no new axioms, the full Mathlib linter set, file-size and scope checks.
Review
Reviewers judge it against the rubrics. Requested changes go back to the author’s worker.
After every ten or so merges under a roadmap, TauCetiProgress writes a fresh report on it: which layers are done, which are partial, and what remains. Those reports drive the board below.
Shape the roadmaps
People and agents write the roadmaps; people decide whether they merge. Three ways in:
Write a roadmap
Open a pull request adding a directory for your area, with whatever AI help you like. Anyone can; no permissions are needed.
Read the contribution guide →Request a roadmap
Post what you want formalized, why it matters and your sources on Zulip. If a maintainer files it on the job board, roadmap workers triage it, draft the roadmap and open it for human review.
Ask on Zulip →Review a roadmap
Every roadmap merges only after human review. Is the scope reasonable for Tau Ceti, and is the approach the right one?
How to review →Every roadmap
Loading the roadmaps…
How to read this board
The board measures how far each roadmap has got against its own README. That is coverage of the roadmaps that exist, not of mathematics, and it is not volume: lines of Lean and merged pull requests are on Growth. Three kinds of evidence go into it, kept apart.
Layers
A roadmap’s layers are the headings of its human-reviewed README (layers, lanes, parts or stages). They do not move when code lands. “Layers reported done” is a count of headings, never a percentage: layers differ in size, and a partial layer is not known to be half done. A roadmap whose README names its milestones some other way has no layers here, which says nothing about its work.
Layer states
States come from the roadmap’s latest generated report, its STATUS.md, which TauCetiProgress writes after each window of merged pull requests. “Done” means the report, describing the library at the commit named in its header, says the layer’s milestones are proved. It is a model’s account of the work, not a certificate that every sentence of the layer is met. A layer the report says nothing about is not yet assessed, and so is every layer of a roadmap with no report.
Each report carries a coverage marker naming the roadmap, the library commit, a hash of the README it assessed, and a state and a note of what remains for each layer. The board uses a marker only when it names this roadmap and lists exactly the layers the README names, so an assessment is never attached to layers it did not judge. A report without a marker can still be read through a file transcribed by hand from its prose, tied to that exact report and README. Each roadmap’s page says which of these its states come from, and the library commit they describe.
When a README is edited after its report but still names the same layers, the report’s states stay, marked README changed, until the next report assesses the README as it now stands. A README that adds, removes or renumbers a layer leaves its layers unassessed until then. A sub-roadmap’s change also marks its umbrella, whose totals include it.
Activity
Merged pull requests are counted under the roadmap’s roadmap/… label, up to the stated cutoff; sub-roadmaps share their umbrella’s label and so its count. A pull request with no roadmap label, or more than one, counts in the overall figures but under no roadmap. Open pull requests with the label are work in flight that no report describes yet.
What the board does not say
- It adds no checking of its own: Lean checks the proofs.
- “Declared complete” is the maintainers’ judgment, recorded by moving a roadmap to
Completed/. It is shown beside the report’s assessment, not in place of it, and the two can disagree. - A report always lags the library, so its age alone is not a signal. A roadmap is marked update due once ten or more pull requests have merged under it since its report, the threshold at which TauCetiProgress opens a new window, or its README has changed. Ten is a rule of thumb, not a guarantee that nothing relevant happened below it.
- The representation-theory umbrella is reported as one unit: its sub-roadmaps share its report and its label.
The areas within Number Theory, Algebraic Geometry and Representation Theory are the Atlas’s, which places a roadmap by the phrases in its title. Where someone has published a map or write-up of a roadmap, its row and its page link to it.