runbooks/
Operational
Runbooks
The artefacts a responder picks up under pressure — incident, migration, and rollback runbooks — as designed documents with structure, calibration, and lifecycle, distinct from the operational disciplines they execute.
3 topics in this section
runbooks/incident/
Incident Runbook
The artefact a responder picks up at 3 AM when a specific class of incident fires — recognising that the runbook is the moment-of-truth interface between institutional knowledge and individual responder bandwidth, and that its structure, calibration, and discoverability determine whether the responder resolves the incident or compounds it.
→
runbooks/migration/
Migration Runbook
The artefact that turns a multi-week, multi-team, often-irreversible system change into an executable, gated, rollback-aware project — recognising that migrations are where the architectural complexity of the old and new systems collide, and where the runbook's structure determines whether the migration ships cleanly or accumulates as the next quarter's tech debt.
→
runbooks/rollback/
Rollback Runbook
The artefact that captures how to undo a change that's already been deployed — recognising that the rollback runbook is what makes forward velocity safe, that an untested rollback plan is no plan at all, and that the design of the rollback path is itself an architectural property of the change being rolled back.
→