2026-04-incident-template.md
markdown
sha256:c2dbf04d56308f3bbf2d06e6d2eb022b8948b1e827195fe525a44e5e18d5f9c0
feat(auth): Phase B Connect cloud agent (RFC 8628) + Hermes…
Human
minor
⚠ breaking
11 days ago
title: "Incident template — copy for each production incident" project: engineering-team-template tags:
- incident
- template
- sre date: 2026-04-07
Incident — [TITLE] (TEMPLATE)
Severity: SEV? | Status: investigating | Incident commander: [name]
Summary
One or two sentences on user-visible impact and scope (regions, percent of traffic).
Timeline (UTC)
- HH:MM — alert fired [link]
- HH:MM — mitigation started [action]
- HH:MM — restored / degraded mode
Impact, cause, mitigation
Impact: cohort affected; duration; SLA/revenue (internal—link finance if needed). Root cause: technical finding after evidence vs process/capacity factors. Mitigation: rollback, scale, shed traffic, flags, etc.
Follow-up & lessons
Track actions (alerting, patches, runbook edits) with owner and due. Capture what sped response vs what slowed detection. Replace brackets; one file per incident; link tickets and the postmortem.
File History
1 commit
sha256:93bcf8f9bd56d8c5b9339f4ec73b9ebd66571398d56262d38eedc2cfa9db9882
fix(test): align Band B landing assertion with desktop MCP …
Human
11 days ago