SYSTEMA CONSTRUCTUM

Accepted ontology entry

runbook

A runbook is a structured, documented set of step-by-step procedures designed for executing routine operational tasks, performing troubleshooting, and responding to incidents in a consistent and repeatable manner. It is created by organiza…

ACCEPTED THINGcms9c3xo800r17skqn8wz42lo

Definition

A runbook is a structured, documented set of step-by-step procedures designed for executing routine operational tasks, performing troubleshooting, and responding to incidents in a consistent and repeatable manner. It is created by organizations to standardize practice, reduce errors during high-pressure situations, and preserve institutional knowledge so that operators without deep expertise can perform complex tasks correctly. The runbook persists as a maintained reference document or knowledge-base entry, updated as procedures evolve. [formal: liber manualis | substrate: behavior | horizon: hours | explicit: yes | epoch: 0.01]

Why it is in scope

A runbook is a human-made, structured document containing step-by-step procedures for executing routine operations, performing troubleshooting, and responding to incidents. It exists to standardize operational practice, reduce cognitive load during high-stress events, and preserve institutional knowledge — designed to persist as a reference artifact that any operator can consult.

Names and aliases

Relations from this entry

  • cmru73a3j0073r671nhkzxpfxINSTANCE_OF →

    A runbook is a specific kind of procedure — specifically, a documented step-by-step procedure for operational tasks. Any competent operator would describe a runbook as 'a procedure.' The nearest kind is procedure (not documentation, which is the format, or playbook, which is a different genre of procedure).

  • cmrz2cszc02s2ekkxlce5xklsINSTANCE_OF →

    A runbook is a specific kind of documentation: a set of operational procedures designed to handle common scenarios and problems. Per Law 9, a runbook is a kind of documentation artifact. A competent speaker would call a runbook 'documentation'.

  • cmsip7bsg00pinobpjm0rpp62SERVES →

    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).

Relations to this entry

No accepted relations in this direction.

Record identity

Created
Jul 31, 2026, 7:27 PM UTC
Content hash
4152e6b364df2540cdd1eec3fc8b23b8c899a21a187ca17fb6f311ed64eaa2a0

Open a related act record