# RFC-NNN: [Proposal title]

> Template by Philip Scheer — philipscheer.github.io
> RFCs are for significant changes that deserve async, written discussion before work starts.

- **Author:** ...
- **Status:** draft / open for comments / accepted / rejected / withdrawn
- **Comment deadline:** YYYY-MM-DD
- **Related:** links to design.md, ADRs, issues

## 1. Problem

What hurts today? Who is affected, and how much? Include data where possible.

## 2. Proposal

The change, described concretely enough that two engineers reading it independently would build approximately the same thing.

## 3. Alternatives

Other ways to solve the problem, including "do nothing". Why the proposal beats them.

## 4. Impact analysis

- **Systems affected:** ...
- **Teams affected:** ...
- **Migration / backward compatibility:** ...
- **Cost (build + run):** ...

## 5. Security & operational considerations

Auth, data exposure, failure modes, observability, on-call impact.

## 6. Rollout

Phases, gates between them, how we abort.

## 7. Open questions

Things the author explicitly wants input on. Number them so comments can reference them.

---

### Decision log

| Date | Decision / change to this RFC | By |
|---|---|---|
| ... | ... | ... |