---
title: "RFC-XXXX: &lt;Title&gt;"
description: One-line summary of this RFC.
---

# RFC-XXXX: &lt;Title&gt;

| | |
|---|---|
| **Status** | Draft |
| **Author** | |
| **Phase** | |
| **Created** | YYYY-MM-DD |
| **Supersedes** | — |
| **Superseded by** | — |

## Summary

[One paragraph overview of what this RFC proposes and why.]

## Motivation

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

## Detailed design

[The substance of the proposal. Include interface signatures, SQL schemas, protocol details, or whatever is being standardized. Be specific enough that two engineers independently implementing from this RFC would produce compatible results.]

## Drawbacks

[Known costs, risks, or reasons NOT to do this. Be honest.]

## Alternatives considered

[Other approaches evaluated and why they were not chosen.]

## Unresolved questions

[Open items that must be resolved before this RFC can be accepted. List blockers explicitly.]

## Implementation notes

[Post-acceptance: migration path, estimated timeline, affected files, rollback strategy if any.]
