RFC openings that invite comments instead of crickets

Open with context links and a crisp problem statement. If readers must scroll to learn why the doc exists, they will skim everything that follows. Add a “non-goals” section early so reviewers do not argue about scope you already ruled out.

Invite dissent with explicit prompts: “We are uncertain about storage costs—poke holes in assumption B.” That sentence pattern signals psychological safety while staying professional.

End with a decision deadline and how feedback will be integrated. Async cultures stall when authors forget to close the loop. Borrow the recap checklist from Writing RFCs and Design Notes to announce what changed after comments land.