// the take
This is PagerDuty's own incident-response playbook, published as a public MkDocs site: role definitions (incident commander, scribe, liaisons), severity levels, chatops examples, post-mortem templates, and training materials. It's for engineering managers or SRE/platform teams who need to stand up an on-call and incident process and don't want to write one from scratch.
The process comes from a company whose entire product is incident management, so the severity levels, escalation flow, and role split (IC vs scribe vs liaison) are genuinely battle-tested rather than theoretical. The post-mortem template and anti-patterns doc are concrete enough to copy into your own wiki with minimal editing. It covers the people side as much as the tooling side - call etiquette, blameless post-mortems, training slides for onboarding new on-call engineers - which most 'incident response' repos skip entirely.
It's written around PagerDuty's own tooling and culture - the chatops screenshots assume Slack + PagerDuty specifically, so anyone on a different stack is translating, not copying. There's no automation here: it's prose and templates, not a CLI or integration you install, so adopting it means manually porting content into your own docs system. As a public-facing corporate doc site it's also not something you'd fork and iterate on as a living internal doc - expect to diverge from upstream quickly once you adapt it.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →