Build · Create · Engineering
Incident response playbook
A severity-tiered response playbook (roles, response targets, escalation, comms) so responders follow a plan instead of debating process mid-outage.
You receive: A structured playbook (JSON) that passes the severity-coverage, ordered-target, role, escalation, and comms checks.
Part of Keep App Running
What's verified: STUD verifies the submitted playbook (JSON) covers exactly your required severity levels, each with a positive response target that is monotonic by severity (more severe gets an equal-or-tighter target), the minimum steps per severity, roles drawn from your allowed set, uniquely ordered steps, an escalation path where required, and comms channels. STUD does NOT judge whether the targets are achievable or whether the plan will actually resolve an incident; it checks the playbook's structure and consistency.
Opens soon
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
Service
stud-platform
Severities
- eng-lead
- vp-eng
- #incidents
| Order | Role | Action |
|---|---|---|
| 1 | on-call | Acknowledge the page and confirm scope: is stud.com down, or is the judge verification pipeline failing to settle runs |
| 2 | ic | Open the incident channel, assume incident commander, and post an initial status line |
| 3 | on-call | Check the latest production deploy and the Neon database connection for the fault |
| 4 | eng-lead | Decide rollback to the last known-good deploy or a forward hotfix, and execute it |
- eng-lead
- #incidents
| Order | Role | Action |
|---|---|---|
| 1 | on-call | Confirm the queue depth for pending judge runs and check for a stuck build |
| 2 | on-call | Check the judge route's function logs for repeated timeouts |
| 3 | comms | Post a status note to the support channel: run verification is delayed, no data loss |
| 4 | eng-lead | Restart or scale the affected function, then confirm the queue drains |
- eng-lead
- #bugs
| Order | Role | Action |
|---|---|---|
| 1 | on-call | Reproduce the reported play defect and confirm it does not block settlement elsewhere |
| 2 | on-call | File the defect against the play's slug and label it non-blocking |
| 3 | eng-lead | Schedule the fix in the next groom-and-ship cycle rather than paging |
Get early access to STUD the day it goes live.