Specs¶
Specs live in the project wiki, not in this repository.
A spec is a point-in-time decision record — written once, true of a moment, read
later for its conclusions. Keeping them here buried the living documentation they
sat beside, so they moved. Contributor guides, engineering standards and testing
conventions stay in docs/, because those change with the code.
| Spec | Title | Status |
|---|---|---|
| 0001 | rtb-app v0.1 | IMPLEMENTED |
| 0002 | rtb-assets v0.1 | IMPLEMENTED |
| 0003 | rtb-cli v0.1 | IMPLEMENTED |
| 0004 | rtb-config v0.1 | IMPLEMENTED |
| 0005 | rtb-credentials v0.1 | IMPLEMENTED |
| 0006 | rtb-error v0.1 | IMPLEMENTED |
| 0007 | rtb-telemetry v0.1 | IMPLEMENTED |
| 0008 | Rust Tool Base — Requirements & Specification | DRAFT |
| 0009 | rtb-docs v0.1 | IMPLEMENTED |
| 0010 | rtb-redact v0.1 | IMPLEMENTED |
| 0011 | rtb-update v0.1 | IMPLEMENTED |
| 0012 | rtb-vcs v0.1 | IMPLEMENTED |
| 0013 | v0.2 scope — roadmap refactor and rtb-vcs split | IMPLEMENTED |
| 0014 | rtb-config — subscribe() + hot reload (v0.2 addendum) | IMPLEMENTED |
| 0015 | rtb-telemetry — HttpSink + OtlpSink (v0.2 addendum) | IMPLEMENTED |
| 0016 | rtb-ai v0.1 | IMPLEMENTED |
| 0017 | rtb-mcp v0.1 | IMPLEMENTED |
| 0018 | v0.3 scope — rtb-ai + rtb-mcp | IMPLEMENTED |
| 0019 | rtb-cli ops subtree v0.1 (slice 2 of v0.4) | IMPLEMENTED |
| 0020 | rtb-tui v0.1 | IMPLEMENTED |
| 0021 | v0.4 scope — rtb-tui + cli ops subcommands | IMPLEMENTED |
| 0022 | v0.4.1 scope — App |
IMPLEMENTED |
| 0023 | v0.5 scope — rtb-vcs v0.2 git-operations slice | IMPLEMENTED |
| 0024 | v0.6 — rtb-cli-bin scaffolder (rtb generate / rtb regenerate) |
IMPLEMENTED |
| 0025 | Scaffolder setting verb — rename config-field and complete the remove triad |
IMPLEMENTED |
| 0026 | MCP command exposure gating v0.1 | APPROVED |
| 0027 | rtb-update self-update policy v0.1 | IMPLEMENTED |
| 0028 | Scaffolder custom-template overlays v0.1 | APPROVED |
| 0029 | Scaffolder feature-toggle (rtb enable/disable) v0.1 | APPROVED |
| 0030 | Documentation corrections from the GTB parity audit v0.1 | APPROVED |
| 0031 | rtb-app regex_util::compile_bounded v0.1 | APPROVED |
| 0032 | rtb-cli browser::open_url v0.1 | APPROVED |
| 0033 | rtb-cli changelog subcommand v0.1 | APPROVED |
| 0034 | rtb-error process exit-code attachment v0.1 | APPROVED |
| 0035 | Scaffolder CI-pipeline scaffolding v0.1 | APPROVED |
| 0036 | Scaffolder command-authoring parity v0.1 | IN PROGRESS |
| 0037 | Scaffolder generate-project git push v0.1 | APPROVED |
| 0038 | Preset-aware scaffolder codegen (generate command / flag) | IMPLEMENTED |
| 0039 | Rust CI build & test performance | APPROVED |
| 0040 | Build & CI performance under the multi-repo topology | APPROVED |
| 0041 | Crate extraction playbook — standard repo framework & per-repo procedure | APPROVED |
| 0042 | GTB ecosystem re-comparison — parity audit phase 3 | APPROVED |
| 0043 | Multi-repo decomposition — strategy & target topology | APPROVED |
| 0044 | rtb-config v2 — a Store architecture, informed by GTB config v0.3+ | APPROVED |
Referring to a spec¶
By number and name — "0020, the explainable-cull spec" — never by date. The number is a stable handle; a date is not something anyone remembers.
Writing a new one¶
Claim the next number first, then draft against the canonical shape. See the
spec-driven-development skill in the phpboyscout marketplace.