Repository navigation
History RFCs index
TeamCLI's public RFCs — numbered proposals that 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. 000–009 are accepted.
The series is being re-laid into four tiers — the Charter (Tier 0), the Kernel (Tier 1), the Runtime (Tier 2) and the seven modules (Tier 3). The Charter and the Kernel are published; the Runtime is forthcoming, and the modules below (002–009) stay in their current form until each is re-laid.
| # | Subject |
|---|---|
| RFC 000: The Charter (Tier 0) | What we believe, what a team is and how it lives, and how we decide. Re-laid from Foundation; accepted 2026-10-11. |
| RFC 000: Foundation | Replaced by the Charter on 2026-10-11; kept as history. |
| The Kernel (Tier 1) | The one enforced layer of authority, capabilities and trust; absorbs RFC 001 and the enforced half of RFC 009. Accepted 2026-10-09. |
| The Runtime (Tier 2) | Forthcoming — not yet published. |
| RFC 001: Security | What TeamCLI commits to, and what it does not protect you from, when agents operate the tool. |
| RFC 002: Communication | How a thing said reaches the one it is for. |
| RFC 003: Memory | What a team knows tomorrow that it learned today, and who decided so. |
| RFC 004: Analysis | Looking at a project, a team and its work, and saying what was found. |
| RFC 005: Quality | What makes work done, who says so, and what a check is worth. |
| RFC 006: Consensus | How several voices become one decision that can be relied on. |
| RFC 007: Harness | Starting a team and keeping it running. |
| RFC 008: Planning | A team reads its own backlog, plans it and runs it; the tracker is an adapter. |
| RFC 009: Roles & Skills | A team is staffed from reusable role and skill libraries, bound per project, context and task. |
How a public RFC is decided is in RFC 000 Foundation (Part 3) and RFC 006 Consensus: reviewers first, in rounds with the text frozen, then the board's vote. A public RFC states its commitments, their costs and limits, what would change our mind, and what is true in the released version today.