# RFC-NNN: Title

| Field | Value |
|-------|-------|
| RFC | NNN |
| Title | Short descriptive title |
| Author(s) | Your Name |
| Status | Draft / Accepted / Implemented / Superseded |
| Created | YYYY-MM-DD |
| Updated | YYYY-MM-DD |
| Replaces | — |
| Superseded by | — |

---

## Summary

One paragraph: what this RFC proposes and why.

---

## Motivation

Why is this change needed? What problem does it solve? What happens if we don't do this?

---

## Detailed Design

The core of the RFC. Be specific and concrete. Include:
- Data structures / schemas
- API contracts
- Behavioral specifications
- Error handling
- Edge cases

Use code blocks, diagrams, and tables liberally.

---

## Drawbacks

What are the downsides? What complexity does this add? Are there performance implications?

---

## Alternatives Considered

What other approaches were considered and rejected? Why?

---

## Unresolved Questions

What is still unclear or deferred? These should be resolved before the RFC is accepted.

---

## Implementation Plan

High-level breakdown of how this will be implemented. Reference the progress-tracker.md tasks if applicable.
