How we use RFCs

RFC ("Request for Comments") is our default mechanism to shape complex work before implementation. It is collaborative, async, and designed to expose flaws early.

RFC types

• Idea proposal
• Complex bug analysis
• New feature discovery and planning

Why RFCs

They improve remote collaboration, increase scope clarity, support deep research, and build consensus without forcing premature commitment.

Template

• Purpose
• Background
• Proposal
• Technical details
• Implementation plan by phases
• General questions
• Open questions

Discussion workflow

RFCs start as Markdown (repo docs, GitHub Discussion, or a shared doc), are announced in team chat for async review, revised in the open, and marked approved when tradeoffs are explicit and owners agree.