zoom-outlisted

# Zoom Out (FR-20) > **Style:** Mode-B-lite. Concise, structured, AI-consumable. ## Purpose Stop patch-myopia. Before fixing a bug or making an improvement, zoom out and confirm the change addresses the root cause and stays consistent with the bigger picture — instead of stacking a narrow patch that creates drift elsewhere. Operationalizes always-on rule FR-20. ## When to invoke - About to commit a bug fix or behavior change that is non-trivial. - The same file / function / area has been patched before (repeat-patch smell). - A fix touches shared logic, data shape, an interface, or cross-app behavior. - Operator says "fix X", "why does X keep breaking", "patch", "quick fix". - Active phase is Implement or a post-gate fix. ## Do not invoke when - Trivial typo / formatting / comment-only edit. - Pure net-new feature with no existing code to reconcile against. - The work is reproduce-before-fix itself (that is FR-10 / `validation-and-qa`) — run that first, then zoom out on the fix design. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | The observed symptom / bug | operator report, logs, test output | run reproduce-before-fix (FR-10) first | | Spec / decisions (if under a ticket) | `docs/specs/<slug>/` | proceed; note no spec to check against | | North Star (if present) | `docs/north-star.md` | skip the North-Star check silently (absent-by-default) | ## Procedure 1. **Name the symptom vs the cause.** State the visible failure, then the underl