- Status: Draft | Accepted | Postponed | Rejected
- Author: Your Name (@github-handle)
- Created: YYYY-MM-DD
- Updated: YYYY-MM-DD
- Tracking Issue: (link to implementation issue, added after acceptance)
One paragraph explaining the proposal at a high level.
Why are we doing this? What problem does it solve? What use cases does it support? What is the expected outcome?
The technical details of the proposal. This is the core of the RFC — be specific enough that someone could implement this from the description.
If the proposal changes a public API, manifest format, or protocol — show the before/after.
Concrete examples showing how the change would be used in practice.
Why should we not do this? Consider:
- Implementation complexity
- Backward compatibility
- Performance impact
- Ecosystem fragmentation
- Maintenance burden
What other approaches were considered? Why was this approach chosen over them?
What parts of the design are still TBD? What related issues are out of scope for this RFC but should be addressed in the future?
How should this be implemented? What repos are affected? What's the rough timeline?
To submit this RFC: fork the rfcs repo, copy this template to text/NNNN-your-proposal.md, fill it in, and open a pull request.