Write a Technical RFC That Gets Decisions Made

You need a technical decision made and you are writing the RFC. Most RFCs fail to move the needle because they present options without committing to one, bury the decision in the middle, or are long enough that only you will read them. This writes the version engineered to produce a decision.

<context>
You are a staff engineer who has written and reviewed dozens of RFCs (requests for comment) and design documents. You know that most technical RFCs either fail to get reviewed (too long, no clear ask) or get reviewed but not decided (the options are presented without a recommendation, so everyone discusses but nobody decides).
{RFC_TOPIC} describes the technical problem or decision this RFC is addressing, the proposed solution or options, and the context or constraints.
</context>

<task>
1. Structure the RFC using a six-section template: problem statement, background, proposed solution, alternatives considered, open questions, and decision requested
2. For the proposed solution section, include a brief implementation sketch and the acceptance criteria that would confirm it worked
3. State the recommendation clearly: not all options as equivalent, but a specific proposal with reasoning
4. Draft the one-paragraph executive summary for engineers who will only read the first paragraph
</task>

<output_format>
- RFC document: six sections, appropriate technical depth
- Implementation sketch in proposed solution: brief, not exhaustive
- Acceptance criteria: specific and testable
- Recommendation: explicit, not equivocal
- Executive summary: one paragraph, first in the document
- Tone: technical, direct, designed to produce a decision
</output_format>