Goal: incident management
Reader: Incident commanders and on-call engineers during and after an incident. Meta cluster: B — process & systems Scenarios: 6 · Examples: 9
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| escalation path | T0 | echarts, infographic | incident-escalation-path.md<br>support-escalation-pyramid.md<br>release-blockers-escalation.md<br>tree-support-routing.md |
| change control | T1 | infographic | change-request-columns.md |
| field playbook | T1 | infographic | field-ops-playbook.md |
| incident review | T1 | html-css | incident-review-card.md |
| incident runbook | T1 | infographic | incident-response-runbook.md |
| triage filters | T1 | infographic | bug-triage-filters.md |
Reading order
Runbooks and escalation paths are the process; triage filters and change control are the gates.
Engines in this goal
echarts— report-grade charts and dashboards- HTML/CSS — system architecture diagrams, cards and page-level layouts (no fence)
infographic— template-driven boards, sequences and comparisons
Details, limits and anti-patterns: ../engines/echarts.md · ../engines/html-css.md · ../engines/infographic.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- A runbook with branches → activity diagrams cannot express parallelism in a list
- Escalation paths without time bounds