2026-04-incident-template.md
markdown
sha256:8d46372e39d2d5a54fd93a8b1c27922fe0d9b22a72197345f1d2c71701cc4ce2
feat(auth): persistent login system + C7 session introspection
Human
minor
⚠ breaking
16 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
2 commits
sha256:8d46372e39d2d5a54fd93a8b1c27922fe0d9b22a72197345f1d2c71701cc4ce2
feat(auth): persistent login system + C7 session introspection
Human
minor
⚠
16 days ago
sha256:6a102aafafdfe7e70a24f4e59740200f0ee713ce7915f1b53e9d4ba5ee8b4410
Initial Muse snapshot
Human
48 days ago