Runbooks¶

Concrete, step-by-step operational runbooks. One page per procedure. (This page is the index — create one section per runbook as procedures stabilize.)

Index¶

Runbook	Status
Deploy a static site (Cloudflare Pages)	Done
Deploy a VPS service	Done
Incident response	Done
VPS prd1 provisioning from scratch	[TODO: write]
Database restore drill	[TODO: write]
Offboarding procedure	[TODO: write]
New client onboarding (implementation)	Done (skeleton)

Writing a runbook¶

Every runbook should answer, in order:

When to use it — trigger conditions.
Expected outcome — what "done" looks like.
Steps — numbered, copy-pasteable commands.
Rollback — how to undo step 3.
Verification — how to confirm success.
Owner — who maintains this runbook.

# <Title>

## Trigger
## Expected outcome
## Steps
## Rollback
## Verification
## Owner

Runbooks are tested

If a runbook was not executed in the last 6 months, schedule a drill. Untested runbooks are fiction.