Nobody should start an incident from nothing.
A page fires at 3am. The workspace comes up with the runbook, the last four deploys, the logs and every prior incident on that service, so the first ten minutes are not spent finding out what changed.
The shape
Trigger, context, workspace.
Everything between the event and the first turn is gathered by an automation, so the agent never starts from nothing.
Trigger
PagerDuty · P1
checkout-api error rate 12%
Sustained for 6 minutes. Paged at 03:14.
Gathered first
- The service runbook and its escalation path
- The last four deploys, with diffs and who shipped them
- Error logs and traces for the affected window
- Every prior incident on this service
- Current dependency health
Composed of
incident-response
- mcp
- datadog, pagerduty
- tools
- github
- ttl
- 4h
Nobody is grepping dashboards half awake. The workspace comes up knowing what changed and what broke last time.
What it displaces
Before and after.
Six browser tabs and a Slack search at 3am
One workspace with all six already in it
"Has this happened before?" asked into a channel
Every prior incident on this service, already loaded
A runbook that assumes you know which dashboard
The dashboards, fetched before you arrived
Also