π‘ RFCs (Requests for Comments)
1 / 1
| Title | Author | Status | Date βΌ |
|---|---|---|---|
| RFC-001: React 19 Upgrade & Frontend Alignment | relbns | draft | 2026-06-18 |
What lives here: detailed proposals for significant changes β multi-team scope, contract-changing, week-plus work, with formal comment period and discussion.
Use vs. siblings: a proposal is lighter (side-project, single-engineer); a PRD is for an already-agreed feature about to be built; an ADR records the decision after it's made. An RFC is the open-question phase.
Template: RFC Β· filename:
docs/rfcs/rfc-<slug>.md
An RFC is how we propose significant changes to the product or platform before implementing them.
When to write an RFCβ
Write an RFC when the change:
- Affects more than one team
- Changes a public API or data contract
- Has non-obvious trade-offs worth discussing
- Requires a week or more of engineering work
For small, contained changes β just open a PR.
RFC lifecycleβ
Draft β Open for Comment (7 days minimum) β Accepted / Rejected β Implemented / Closed
Indexβ
| # | Title | Status | Author | Date |
|---|---|---|---|---|
| No RFCs yet β see the RFC template to draft the first one. |
tip
Use the RFC template. Comment period is minimum 7 calendar days before a decision.