Skip to content

Runbooks & On-Call

Home / Guides & Runbooks / Runbooks & On-Call

Step-by-step procedures for recurring operational tasks and incident response. A good runbook is something a teammate can follow at 2 a.m. without context — keep each one concrete, sequential, and tested.

Scaffold — add runbooks as procedures are formalized

Start a new ## Runbook: … section for each procedure. When a runbook gets long, split it into its own page under guides/.

On-Call

  • TBD: rotation, escalation path, how to acknowledge and hand off.

Runbook: Deploy the Docs Site

The wiki deploys automatically — pushing to main triggers a Cloudflare Pages build.

  1. Merge your change to main.
  2. Watch the Cloudflare Pages build for the docs project.
  3. Verify the live site once the build is green.

Runbook: Rotate a Leaked Credential

  1. Identify the affected system in the Systems Registry.
  2. Revoke the exposed key/token in that system.
  3. Issue a replacement and update every consumer (env vars, GitHub Actions secrets, ~/.mds/config.toml, etc.).
  4. Note the rotation and confirm the old credential no longer works.

Runbook: Incident Response