## Goal

Apply production changes with predictability, reversibility, and clear communication.

## Change cycle

<Steps>
  <Step title="1) Classify change">Define low-risk, high-risk, or breaking, and list impacted teams.</Step>
  <Step title="2) Prepare validation">Ensure tests, rollback criteria, and explicit execution owner.</Step>
  <Step title="3) Execute in proper window">Avoid external risk windows and confirm on-call coverage.</Step>
  <Step title="4) Verify post-release">Monitor core metrics and close only after sustained stability.</Step>
</Steps>

## Decision matrix

| Type | Minimum approval | Rollback requirement |
| --- | --- | --- |
| Low-risk | technical owner | recommended |
| High-risk | technical owner + operations owner | required |
| Breaking | technical owner + operations owner + external communication | required |

## Relationship with changelog

Every production change should include changelog context with:

- release timestamp;
- expected impact;
- mitigation path if needed.