Repository navigation
RFCs
TeamCLI's public RFCs state, in plain language, what the tool commits to and what it does not. Each is reviewed by at least three reviewers from three different labs (none the author's lab) over rounds until they are unanimous, then accepted by the board. A commitment names the spec section that implements it and the test that proves it, where one exists.
The series is laid out in tiers: the Charter (Tier 0), the Kernel (Tier 1), the Runtime (Tier 2), the modules (Tier 3), and the governance texts. A page marked draft may change; an accepted page changes only by a new amendment that names what it supersedes.
| Tier | Page | Status | Subject |
|---|---|---|---|
| 0 | Charter | Accepted — 2026-10-11 | What we believe, what a team is and how it lives, and how we decide. |
| 1 | Kernel | Accepted core; sections from amendments 01–03 draft | The one enforced layer of authority, capabilities and trust. |
| 2 | Runtime | Draft — may change (2026-10-19) | What the Runtime keeps, runs, reads and delivers, so that a team is started, known, reached, watched, stopped and put right. |
| 3 | 002 Communication | Draft — may change (2026-10-19) | How a thing said reaches the one it is for. |
| 3 | 003 Memory | Draft — may change (2026-10-19) | What a team knows tomorrow that it learned today, and who decided so. |
| 3 | 004 Measurement | Draft — may change (2026-10-19) | Looking at a project, a team and its work, and saying what was found. |
| 3 | 005 Quality | Draft — may change (2026-10-19) | What makes work done, who says so, and what a check is worth. |
| 3 | 006 Consensus | Draft — may change (2026-10-19) | How several voices become one decision that can be relied on. |
| 3 | 008 Planning | Draft — may change (2026-10-19) | A team reads its own backlog, plans it and runs it; the tracker is an adapter. |
| 3 | 009 Roles and skills | Draft — may change (2026-10-19) | A team is staffed from reusable role and skill libraries, bound per project, context and task. |
| 3 | 010 Workflow | Draft — may change (2026-10-19) | Who takes a piece of work, who does it, who checks it, and how the owner learns it is finished. |
| Governance | Board | Draft — may change (2026-10-19) | Who decides on a proposal, and the board's composition and rules. |
| Governance | Review terms | Draft — may change (2026-10-19) | The review floor, the rounds, and how a round ends. |
| Governance | Norms and practices | Draft — may change (2026-10-19) | How decisions and living specifications are kept apart, and which outside norms the series follows. |
The living specifications behind these pages are generated, one page per file and per registry, in the Specs index.
The earlier public series — RFC 000 to RFC 009, and the earlier Kernel and Architecture pages — remains readable under History, unchanged apart from links and one outdated term. Its entry point is the earlier RFC index.
A text is reviewed in rounds, frozen at a named commit, by reviewers from different labs; silence is never a yes, and a round ends only in unanimity or in a decision reserved to the board. The Review terms state the floor and the rounds; the Board page states who decides; and Norms and practices states how a decision text and a living specification are kept apart.