quill: add incident notification templates draft

wizard-work/quill/incident-notification-templates.md

@@ -0,0 +1,48 @@
+# Incident Notification Templates
+## Internal and customer-facing drafts for quick copy-paste during an incident.
+
+---
+
+### Internal: Incident Declared
+**To:** #incident-<YYYYMMDD>-NN
+**From:** Incident Commander
+
+> **SEV-<N> declared:** <one-line summary>
+> Impact: <affected services / user segments>
+> Current status: <investigating / identified / monitoring / resolved>
+> Next update: <time>
+> IC: <name> | Scribe: <name>
+
+---
+
+### Status Page Update — Investigating
+> We are currently investigating an issue affecting <service/feature>. Some users may experience <symptom>. We will provide an update within 15 minutes.
+
+---
+
+### Status Page Update — Identified
+> We have identified the root cause as <brief cause>. We are implementing a fix and expect resolution within <time estimate>. We will provide another update in 15 minutes or when resolved.
+
+---
+
+### Status Page Update — Resolved
+> The issue has been resolved. <service/feature> is fully operational. Total impact duration: <X minutes>. A post-mortem will be published within 48 hours.
+
+---
+
+### Executive Summary (for leadership)
+- **Incident:** <title>
+- **Severity:** SEV-<N>
+- **Duration:** <start> — <end> UTC
+- **User impact:** <quantified if available>
+- **Root cause:** <one sentence>
+- **Fixes applied:** <bullet list>
+- **Follow-up actions:** <bullet list with owners>
+
+---
+
+## Usage Notes
+- Replace bracketed placeholders before sending.
+- Keep every message under 3 sentences unless escalation is required.
+- If legal or PII is involved, route all external comms through Comms Lead + Legal.
+- Scribe timestamps every message in the incident channel.