Rollback Risks

# Lens: Rollback Risks

> Reusable analysis lens. Decide whether the change is safely reversible, and what to do if it isn't.

## Purpose
Force an explicit rollback verdict before shipping. Identify data-shape changes that block rollback, define the feature-flag plan, and quantify blast radius if the change ships broken.

## Length budget
**≤25 lines.** Verdict is one label. Runbook is 3-5 numbered steps, one line each. No discussion of options not taken.

## When to use
- Every story before merge.
- Mandatory if the change touches persisted state, public APIs, payment / auth / sync logic, or runs at scale (>1 % of traffic).

## Inputs expected
- Assembled story context.
- Output of `state-changes.md` lens (reversibility verdict per store).
- Discovered deployment / flag conventions from project context.

## Output template