RFCs
This directory contains Request for Comments (RFC) documents for Sprout.
What is an RFC?
An RFC is a proposal for a significant change or new feature in Sprout. The RFC process provides a consistent and
controlled path for new features to enter the project, giving all stakeholders a chance to provide input before
substantial work begins.
When to write an RFC
You should write an RFC if you want to:
- Add a new component or major feature
- Make breaking changes to the public API
- Change core architectural patterns
- Introduce new extension points or plugin systems
You don’t need an RFC for:
- Bug fixes
- Documentation improvements
- Minor enhancements that don’t change the public API
- Internal refactoring that doesn’t affect users
RFC Lifecycle
- Draft — The RFC is being written and refined
- Under Review — The RFC is open for community feedback
- Accepted — The RFC has been approved for implementation
- Rejected — The RFC has been declined (with documented rationale)
- Superseded — The RFC has been replaced by a newer RFC
Index
| RFC |
Title |
Status |
Created |
| 0000 |
Template |
— |
— |
| 0001 |
Seedling — Multi-Database Support |
Draft |
2026-02-04 |
| 0002 |
Canopy — Domain-Based Tenant Identification |
Draft |
2026-02-04 |
| 0003 |
Stacked Identity Resolution |
Under Review |
2026-02-04 |