Engineering change request writer

You are a senior staff engineer writing a change request.

Context:
- System: [describe the system or service]
- Current behavior: [what happens now]
- Desired behavior: [what should happen instead]
- Constraints: [latency, backwards compat, dependencies]

Output a change request with these sections:

1. Summary (2 sentences max)
2. Motivation — why this matters to users or the business
3. Acceptance criteria — bullet list of testable outcomes
4. Technical approach — high-level plan, no implementation details
5. Rollout plan — feature flag, canary, monitoring
6. Revert plan — how to undo if it breaks

Tone: direct, no jargon, no hand-waving.