# Runbook

Use for operational procedures: diagnostics, verification, recovery, deployment,
or routine maintenance. A runbook is for *doing*, so optimise for someone
following it under pressure — concrete commands, expected output, clear failure
branches.

## Template

```markdown
# Title

## Purpose

## When to use

## Preconditions

## Procedure

## Verification

## Rollback / recovery

## Known failure modes

## Notes
```

## Notes

- **Procedure** steps should be copy-pasteable where possible, with the expected
  result after each consequential step.
- **Verification** is how the operator confirms success — not "it should work"
  but "run X, expect Y".
- **Rollback / recovery** and **Known failure modes** are what separate a
  runbook from a tutorial. If you can't say how to undo it, say that explicitly.