Feature Proposal Template¶
Metadata¶
| Field | Value |
|---|---|
| Proposal ID | FP-YYYY-NNN |
| Owner | Named maintainer or working group |
| Evidence Funnel stage | Signal or Discovery |
| Intended maturity | experimental, preview, stable, enterprise-certified, or deprecated |
| Support level | Research, community, maintained, or enterprise |
| Review date | YYYY-MM-DD |
Problem and Users¶
Describe the demonstrated problem, affected users, evidence source, frequency, severity, and current workaround.
Value and Metrics¶
Define measurable user value, product-health metrics, expected open-source value, enterprise value, and expected return on investment.
Alternatives and Non-Goals¶
List alternatives considered, why existing capabilities are insufficient, and what this proposal will not solve.
Impact Assessment¶
Document architecture, security, privacy, accessibility, performance, reliability, operations, compatibility, sustainability, maintenance, and support impact.
Delivery and Lifecycle¶
Define dependencies, acceptance evidence, tests, documentation, observability, incident response, migration, rollback, deprecation, owner, support duration, exit criteria, and review cadence.
Decision¶
Record accepted, rejected, deferred, or discovery-required with approvers, rationale, and links to RFCs, ADRs, threat models, and issues.