Mitigate fast

Contain the blast radius first, then recover with receipts. Choose a fix flow or See example exception. Exit metric: freezes trigger within 24 hours and recovery finishes inside 7 days.

Tiny receipts — Mitigate (v2025.11)

• m-time-to-freeze: 6 hours average
• m-time-to-recovery: 2.5 days See the receipts

How this lane works

1. Freeze quickly — Follow the matching 10-minute fix flow below. Each one ends with a ready-to-send escalation packet.
2. Log the exception — Record exc- IDs, owner, expiry, and exit criteria in exceptions if you step outside a guardrail.
3. Post receipts — Add quality/adoption deltas to /signals/receipts/v2025.11-mitigate.md and update the release bundle once the issue is clear.

Fix flows

• Teams notifications — Restore toast/badge alerts across devices before calling IT.
• Repo or pipeline access — Confirm membership, branch rules, and run permissions prior to filing a ticket.
• Design System component decision — Decide whether to use, extend, compose, or fork without relitigating.
• Flag not behaving on Staging — Validate env, SDK keys, and targeting before pinging Platform.
• VWO/Bloomreach sanity — Detect duplicate injections, CSP blocks, or wrong keys fast.
• Need a bite-sized runbook? Request a new Fix flow.

Escalate when needed

• Use the Quick-Run checklist before/after every fast fix so the receipts stay traceable.
• When a fix requires more than 10 minutes, escalate to Support IT with the packet from the flow you ran.
• Close the loop by updating ops/releases/YYYY-MM/manifest.json and re-running pnpm run state:build.

Related references

• Navigate Start Here
• Operate playbook canon
• Signal registry
• Mitigate receipts