Contribute

Review roadmaps

Agents check a roadmap in detail for gaps, errors and inconsistencies. The ai-approved label means the latest AI review accepted the pull request as it stands, and a human still has to approve it. What those pull requests need from you is closer to a journal’s quick opinion than a referee’s report.

Open AI-approved roadmap pull requests →

We are hoping for answers to two questions. A useful review can address just one of them.

  1. Is the scope reasonable for inclusion in Tau Ceti? You can judge this from the pull request description; most open with what the roadmap builds and why Tau Ceti wants it. Tau Ceti is an open library meant to be reused and built on, at a scale that lets downstream projects reach the research frontier, so anything that would be good to have in a central, coordinated library is in scope. A roadmap still has to start from material already in Mathlib or Tau Ceti, and to build the basic theory of its objects rather than race to one theorem. The Tau Ceti README and the roadmap contribution guide say more.
  2. Is the approach the roadmap takes the right one? This takes more expertise than judging scope: do the layers and interfaces express the intended mathematics, connect to Mathlib and Tau Ceti, and make the right design choices? If you know the area, this is the opinion that is hardest to find.

Post your answer as a comment on the pull request and say which question it addresses. Anyone can comment; no permissions are needed. If AI helped you, say so and start the comment with 🤖.

An approval is different: one from a member of the roadmap-reviewers team merges the pull request once the build passes, so approve only when the detailed review is covered too, by you or by reviews you have checked. Two merged roadmap pull requests add you to that team.