Runbooks

Stefan Coetzeecreated 2026-04-25updated 2026-06-081 min readMOC
Vault note, not reviewed against the source. Written in the knowledge vault on 2026-04-25 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

Operational procedures for common scenarios.

Structure

Each runbook includes:

  • Trigger — When to use this runbook
  • Prerequisites — Access, tools needed
  • Steps — Detailed procedure
  • Verification — How to confirm success
  • Rollback — How to undo if needed
  • Escalation — When and who to contact

Runbooks

Incidents

Operations

  • ☐ Scaling a service
  • ☐ Database maintenance
  • ☐ Log rotation
  • ☐ Backup verification

Security

  • ☑ Credential Rotation — secret rotation, scheduled vs compromise differentiation
  • ☐ Security incident response
  • ☐ Access revocation

Template

# [Runbook Title]

## Trigger
When to use this runbook.

## Prerequisites
- [ ] Access to X
- [ ] Tool Y installed

## Steps
1. First step

command here

   Expected output: ...

2. Second step
   ...

## Verification
How to confirm the issue is resolved.

## Rollback
How to undo changes if needed.

## Escalation
- First: @on-call
- Then: @team-lead
- Finally: @incident-commander