Incident-response is a coordinated organizational practice for managing unexpected service disruptions from detection through post-incident learning. Parameters: triggered by a service-impacting event; structured around detection, escalation, containment, remediation, and post-incident review phases; executed by a designated response team with defined roles. Persistence mechanism: codified in runbooks, playbooks, and incident-command procedures; sustained through drills, training, and lessons-learned processes. [formal: incident-responsus | substrate: behavior | horizon: a moment | explicit: yes | epoch: 0.01]
Accepted ontology entry
incident-response
Incident-response is a coordinated organizational practice for managing unexpected service disruptions from detection through post-incident learning. Parameters: triggered by a service-impacting event; structured around detection, escalati…
Definition
Why it is in scope
A human-made organizational practice for managing and resolving unexpected service disruptions. It involves coordinated actions to identify, contain, remediate, and learn from incidents. Human-made: a structured operational practice codified in IT service management frameworks and organizational procedures.
Names and aliases
- incident-responseen · CANONICAL
Relations from this entry
No accepted relations in this direction.
Relations to this entry
- cmsio9s6c00m7nobpoy6e1smi← SERVES
blameless-postmortem is built for incident-response: its designed purpose is to improve post-incident learning and prevent recurrence, serving the overall incident-response process. Law 8d: for whose sake? servant → master.
- cmsayoaup00pe82b63f3czywq← SERVES
safety-signal is built and maintained for the sake of incident-response: its designed purpose is to alert operators to emerging issues before they become full incidents, serving the overall incident-response lifecycle. Law 8d: servant (safety-signal) points at master (incident-response).
- cmsinr1g700konobpyevl1ud7← DEPENDS_ON
Service reliability engineering needs incident-response to operate: incident response is a core pillar of SRE practice. Removal test — remove incident response from the SRE toolkit and SRE loses a fundamental operational component. This is a genuine dependency, not merely historical association.
- cmsis4lfq00xfnobpcbwh5ojg← SERVES
Chaos-engineering is designed to test and validate incident response — its controlled failures exercise detection, escalation, and recovery workflows that constitute incident response. For whose sake: the chaos practice exists to further incident-response capability.
- cmsj5212h0245nobp0l9o9owq← SERVES
On-call is built and maintained for the sake of incident-response: its designed purpose is to ensure rapid human availability when incidents occur. The servant (on-call) points at the master (incident-response).
- cmsj72bjj028enobpp38qa511← SERVES
An incident-command-post is established and maintained for the sake of incident-response: its designed purpose is to serve as the coordination hub where response teams communicate and track during active incidents. Servant(incident-command-post)→master(incident-response). Law 8d.
- cmsj2z6ab01vvnobp417k0ifi← INSTANCE_OF
An incident-command is a specific kind of incident-response: the practice of establishing structured coordination and decision-making authority during incidents. A competent speaker would call it 'a kind of incident response.'
- cms9c3xo800r17skqn8wz42lo← SERVES
A runbook is a documented procedure for handling specific operational scenarios. Its designed purpose is to support incident response — for whose sake is the runbook built? For incident response. The servant (runbook) points at the master (incident-response).
- cmsj7cy9x02a4nobpjzeyo0z6← SERVES
Blameless culture is a social practice built for the sake of incident response: it creates psychological safety so that teams can report, learn from, and rapidly resolve incidents without fear of punishment. For whose sake is blameless culture maintained? For incident response. The servant (blameless culture) points at the master (incident response).
- cmsj6vomh0280nobpkao0eocu← SERVES
A war room is a dedicated physical or virtual space assembled for the sake of incident response. It exists to coordinate response efforts, concentrate expertise, and accelerate resolution. For whose sake is the war room built? For incident response. The servant (war room) points at the master (incident response).
Record identity
- Created
- Aug 7, 2026, 8:43 AM UTC
- Content hash
- 51dd7902154c43fa762afe391fa8e26f6d6f7dcab66a9a70112e49c9167d45a1