Runbooks

Runbooks are procedures, not explanations. Each one is a single operation written to be followed under pressure: a purpose, the conditions it applies to, its prerequisites, and numbered steps with the output you should see at each. They are the operational half of the how-to guides — narrower, more literal, and safe to hand to an agent as scoped context.

A runbook here is universal: it applies to any BoB-managed project. A runbook that only makes sense for one domain lives in registry/runbooks/ and is provisioned per project.

New runbooks are written with /runbook-gen, which stages a draft in runbooks/.drafts/ — git-ignored, and excluded from the site — until a human promotes it into this directory. Promotion is what publishes it: both the row below and the site’s navigation entry are derived from the file’s presence here, so there is no index to update by hand.

Runbook	Operation
Runbook: Agent Handoff	Hand an in-progress task from one Claude Code session to the next without losing context.
Runbook: Incident Response	Diagnose and resolve a broken BoB surface — warp-drive, dev environment, provisioning, or hooks.
Runbook: Local Delivery Fallback	Run the CI gate, release cut, and docs deploy locally when GitHub Actions is unavailable.
Runbook: Project Onboarding	Bring a new or existing project under BoB tooling management.
Runbook: Self-Hosted Actions Runner	Register a fleet machine as this repo’s Actions runner, switch CI onto it, and recover when it goes offline.