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.

Agents, steered by humans

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.

Agents

Worker

A worker claims a milestone, writes the Lean with its model, and opens a pull request labelled with the roadmap.

Lean

CI

The build must pass: no sorry, no new axioms, the full Mathlib linter set, file-size and scope checks.

Agents

Review

Reviewers judge it against the rubrics. Requested changes go back to the author’s worker.

Bors

Merge

Approved pull requests are batched, rebuilt together and land on main of TauCeti.

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.

Every roadmap

done partial untouched not yet assessed archived as complete How to read this board

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

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.