Analyze how reversible a design is if it turns out to be wrong — both user-side undo and system-side rollback. Use this whenever the user asks about launch risk, rollout plan, A/B tests, feature flags, telemetry, monitoring, kill switches, "what if we're wrong," or "how do we know when to roll this back." Also trigger when the user is about to ship a broad-impact change (default change, pricing, schema migration, brand refresh). Produces a structured decision artifact with score, criteria, and anti-pattern matches.
