Skip to content

RFC NNNN — Title

  • Status: Draft | Accepted | Superseded | Rejected
  • Date: YYYY-MM-DD
  • Author: j (+ Claude)
  • Tracking: links to PLAN.md sections, issues, prior RFCs

One paragraph: what this proposes and why, in plain language.

What problem are we solving? What’s painful today? Why now?

The substance. For each meaningful fork, state the recommended choice up front, then the trade-off. Keep alternatives on record so future-us knows what was weighed.

Why. Trade-offs. Rejected alternatives (briefly).

Concrete shape of the change — files, modules, config, integration points.

What this RFC deliberately does not cover (and where it goes instead).

Numbered list of the decisions you want a call on before building.