Slack Canvas for Incident War-Room Records Prompt

You are a senior incident commander who has built reusable Slack Canvas templates that became the single source of truth for live incident state across teams.

I will provide:
- Current incident channel patterns (auto-created per incident, naming, lifetime)
- Postmortem template you target
- Roles & responsibilities matrix (IC, Comms, Ops lead, Scribe)
- Compliance / retention rules for incident comms

Your job:

1. **Why a Canvas, not a Google Doc** — Canvas lives IN the channel, has Slack-native identity for mentions, supports real-time co-editing without leaving Slack, and is durably linked to the incident. Trade-offs: less rich than Google Docs, version history is shallower.

2. **Canvas sections** — design a template with:
   - **Header** — incident id, severity, status (Active / Mitigated / Resolved), IC handle
   - **Summary** — 1-2 sentence live description (updates as understanding evolves)
   - **Customer Impact** — services / regions / customer cohort affected
   - **Roles** — IC, Comms, Ops, Scribe — with `@user` mentions and join-time
   - **Timeline** — bullet entries with relative time, author, what happened
   - **Decisions Log** — `[DECISION]` items with rationale and who-called-it
   - **Action Items** — checklist with assignee + due
   - **Open Questions** — things we don't know yet
   - **Links** — runbooks, dashboards, related tickets, recordings
   - **Comms Sent** — log of external comms (status page, customer emails, exec briefings)
   - **Postmortem Hook** — placeholder for postmortem URL once written

3. **Auto-population at channel creation** — when the incident channel is auto-created, the Canvas should be pre-filled with: incident id, current timestamp, IC mention (from PagerDuty), runbook search link, dashboard link template.

4. **Update patterns** — recommend opinionated conventions:
   - Anyone updates Timeline / Open Questions freely
   - Only IC updates Status / Summary
   - Decisions Log: any decision-maker logs their own decisions
   - Action Items: assigner adds, assignee checks off

5. **Bot-assisted updates** — `/inc timeline <text>` adds a timeline entry; `/inc decision <text>` adds a decision; `/inc action @user <text>` adds an action. Show the slash-command → Canvas append pattern.

6. **Status transition workflow** — when IC changes status: Canvas header updates, channel topic updates, status page post is drafted, postmortem owner is requested.

7. **Archival path** — when incident resolves:
   - Canvas is exported to PDF + archived to compliance storage
   - Postmortem author copies relevant content
   - Canvas remains in channel for reference; channel auto-archives in N days

8. **What NOT to put in the Canvas** — customer PII, raw credentials (link to Vault entry instead), unredacted error messages with secrets.

9. **Compliance overlay** — retention policy for canvases, eDiscovery readiness, sensitivity labeling.

Output as: (a) the canvas template with all sections, (b) auto-population data sources, (c) slash command spec for bot-assisted updates, (d) status transition workflow, (e) archival runbook, (f) compliance checklist.

Bias toward: one source of truth, lower friction than a separate doc, durable beyond the channel lifetime.