Runbooks

Build · runbook

▶Start here

You are here: Build → Runbooks This type is for you if: you need literal steps for one operation — rollback, restore, incident check. Not this? SOPs = official policy · Playbooks = full phased narrative.

The map

graph TD
  RB["Runbook"] --> Op["Single operation"]
  Op --> Cmd["Commands + checks"]
  PB["Playbook"] -.->|"peel when linkable"| RB

---

Start here

Laravel/CodeCanyon — Runbooks One-operation command cards — code→test→ship, Zaj module deploy, server sync, security updates, doc authoring.

Available runbooks

Category	Cards	Hub
Laravel/CodeCanyon	5	Open hub →

Checklists Gate lists alongside runbooks.

Phase 12 · Production Full production cutover narrative when you need context, not just commands.

Understand everything — when to peel a runbook

When a playbook phase contains commands you’ll run repeatedly (rollback, restore DB), give that slice its own runbook URL. For the official org-wide method, use an SOP instead.