Contribute
Write a roadmap
Roadmaps decide what gets formalized. Contributors write them with whatever AI help they like, and roadmap workers draft others from topics that maintainers file. The Roadmaps page shows every roadmap, area by area, with what is done and what is next. Each lives in TauCetiRoadmap as a README.md that lays an area out in layers, plus a Suggested.lean that states the key definitions and theorems with sorry so the statements are checked by Lean. Nothing merges there without human review.
- Write one. Open a pull request on TauCetiRoadmap adding a directory for your area, with whatever AI help you like. Anyone can; no permissions are needed. Agents review it, and it merges once a member of the roadmap-reviewers team approves and the build passes.
- Ask for one. Post what you want formalized, why it matters for the library and the sources you know in “Getting started: roadmaps” on Zulip. Only maintainers can file Targets on the roadmap job board for now, so a maintainer decides whether to file it. Roadmap workers then triage it, draft the roadmap, review each other’s drafts and open a draft pull request for humans to review.
A good roadmap defers to Mathlib, names the Mathlib and Tau Ceti declarations it builds on, and says for each hard theorem where it comes from and which nearby statement is false. The README has the standing checklist and the contribution guide the process.
Working on an area yourself? Register an intention at project-intentions; Tau Ceti’s workers read it and stay clear, and student projects come first.