Skip to content

Runbooks

Step-by-step operational guides. Each runbook lists required permissions and secrets at the top.

When production is broken, go to Incident Response: severity, the first ten minutes, rollback, break-glass and the review afterwards.

Start with Branching and Releases — it describes how code reaches production in every repository. The other runbooks assume it.

Also here: Deployments (per-service mechanics), the Post-deploy Smoke Checklist (what to check after every production release), Stage Operations (env flips, smoke accounts, outage recipe), Core Server Setup, DSAR Storage and Encryption, the Consent Domain Cutover playbook (partly executed) and the ClickHouse Upgrade record, the Dashboard cutover legacy allowlist spec, the Dashboard Cutover Rollback runbook and stage rehearsal, plus VPN Access, Port Forwarding and Core Dev Database. For support, see Clear a User's TOTP. The reasoning behind how this site is built is under Decisions.