Catalog posture
Severity + system filtered blast-radius lookup
Use this during triage when you know the failing system or the incoming symptom, but still need to confirm customer impact, /beak route exposure, and which runbook gets the first ten minutes right.
Filters
Focus by severity or failing system
Reading guide
What every card captures
Each incident class lists affected journeys, likely Duck Control surfaces, and route-level verification targets. This keeps triage grounded in actual user-facing breakage instead of service names alone.
Runbook starts are intentionally short: confirm signal, freeze risky change lanes, isolate blast radius, then hand off to the deeper runbook or owning service lane.