Writing an RFC

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

A design argued only in chat is hard to inspect or hand off. An RFC gives one proposal a stable working form: the problem forcing it, alternatives weighed against it, and the exact decision requested. If accepted, the durable decision belongs in an ADR; project governance decides whether the RFC itself is retained.

An RFC has these sections: Problem · Proposal · Alternatives · Migration plan · Open questions · Decision requested (walked below). Fill them — this guide is how to fill them well.

The principle: advocate, commit to nothing

An RFC argues for exactly one approach, in enough detail to be judged — and decides nothing. Two failure modes void one: