--- status: draft # draft | accepted | withdrawn | superseded author: start_date: pr: implements: [] supersedes: [] --- # RFC-NNNN: ## Summary One-paragraph non-normative description. ## Motivation Why the status-quo is inadequate. Concrete scenario or user story. ## Design ### Public-facing change What users see / invoke. ### Internal change File paths, types, data flows. ### Backward compatibility Breaking? Deprecation plan? Fallback/opt-in toggle (if any) and removal window? ## Alternatives considered At least two. Why rejected. ## Unresolved questions Open design points the discussion should close. ## Test plan - Unit tests added - Integration tests added - Red-team cases added (if gate/security change) - Benchmark impact (if performance-sensitive) ## Migration If accepted, how existing code moves to the new design. Include rollback plan. ## Prior art Links / papers / projects that inform this. ## Approval checklist (fill in at merge time) - [ ] Reviewer A - [ ] Reviewer B - [ ] Reviewer C (if architectural) - [ ] CI green - [ ] Discussion period elapsed