Communication Templates
Purpose
Copy-paste communication templates for incidents.
Initial notification
[SEV-n] <short title> — investigating
Impact: <who/what>
Started: <time>
IC: <name>
Next update: <time>
Update
[SEV-n] <title> — update
Status: <investigating | identified | monitoring>
What we know: <...>
Next update: <time>
Resolution
[SEV-n] <title> — resolved
Duration: <start>–<end>
Impact: <summary>
Post-mortem: <link>
[stub: comms-stakeholder-list]— fill this in. Greppable doc-debt marker.
Local graph
Linked from 3 notes
Incident Response Playbook
The step-by-step incident response flow for platform-impacting incidents.
04 — Operations & Incident Response
Running the platform: on-call, incident response, runbooks, and post-mortems.
10 — Templates
Reusable authoring templates for ADRs, RFCs, runbooks, post-mortems, and Confluence pages across the ShipSolid platform.
Related notes
Runbooks
Troubleshooting playbooks for every known Signal Forge failure mode, from missing traces to Grafana Cloud export errors.
Alert Runbooks
Runbooks invoked directly from paging alerts.
Incident Response Playbook
The step-by-step incident response flow for platform-impacting incidents.
Incident Trends & Themes
Cross-incident analysis — recurring themes, top contributors, and where to invest.