Build & Create

Playbook · blueprint · SOP · runbook · checklist

▶Start here

You are here: ZajLibrary → Build & Create
This shelf is for you if: you’re ready to design, configure, deploy, or verify something step by step.
Not this shelf? Learn = understand first · Resources = templates and kits · Runbooks = one operation only (peel out of a playbook when needed).

The map

graph TD
  Build["Build & Create"] --> P["Playbooks<br/>multi-phase workflows"]
  Build --> B["Blueprints<br/>design before code"]
  Build --> S["SOPs<br/>official procedures"]
  Build --> RB["Runbooks<br/>exact commands"]
  Build --> CL["Checklists<br/>verification gates"]

---

Start here

Playbooks Phased flows with gates — start with Laravel/CodeCanyon.

Blueprints Architecture and boundaries before you open the repo.

SOPs The canonical org-wide way to do one procedure.

Runbooks Rollback, restore, incident — literal command sequences.

Checklists Pre-merge, pre-deploy, launch sign-off lists.

What’s in this shelf

Type	You get	Best when
Playbooks	Numbered phases + progress	The work has judgment calls and multiple gates
Blueprints	Structure before execution	You need design agreement before coding
SOPs	Policy-backed procedure	The method is official and repeatable
Runbooks	One operation, linkable	You need exact commands without narrative
Checklists	Binary verify list	You need a gate, not a story

Understand everything — playbook vs blueprint vs runbook

• Blueprint = what we’re building and who owns what (pre-build).
• Playbook = how we execute across phases (build → ship → launch).
• Runbook = one slice peeled out for ops (rollback, restore).
• SOP = the approved standard; checklist = did we complete every item?

When a doc grows past ~3 linkable parts, promote it to a folder + index under the right type.