RFC 0000: Title
Status: Draft
Status: Draft
Owner: (maintainer)
Created: YYYY-MM-DD
Related: apps/..., packages/..., docs/...
1. Context
What problem exists today? Link current behavior and observation docs.
2. Goals
What this RFC must achieve.
3. Non-goals
What is explicitly out of scope.
4. Current Architecture
Facts from code and docs/architecture/* — no speculation.
5. Proposal
Recommended approach with diagrams or tables if helpful.
6. Alternatives Considered
Other options and why they were not chosen.
7. Risks
Technical, product, migration, and AI-maintenance risks.
8. Migration Plan
Phased rollout, feature flags, backwards compatibility.
9. Task Breakdown
Numbered slices compatible with task-splitting-protocol.md.
10. Acceptance Criteria
Testable outcomes per phase.
11. Implementation Notes
Filled during/after implementation: deviations, follow-ups, links to PRs.
RFCs (Request for Comments)
RFCs describe **proposed** cross-cutting or high-risk changes before large implementation effort. They complement [architecture decision records](../adr/README.
Architecture Decision Records (ADR)
ADRs capture **one** durable architectural decision: context, decision, consequences, and alternatives. They are smaller in scope than [RFCs](../rfcs/README.md)