Playbooks
What we did, in order, with the evidence. Each playbook is derived from a real Zentari build: the decisions made at each stage, the evidence produced, and what was learned. Not a recommended path — the actual path, with the failures included.
What qualifies as a published playbook
A playbook is published when the build it documents has reached a stage with verifiable outputs and the build log is complete enough to reconstruct the decision sequence. Playbooks in draft are visible in the build logs before they graduate here.
What a playbook covers
Each playbook documents one complete stage or system from a Zentari portfolio company build: the starting conditions, the decisions made and why, what broke and how it was fixed, the evidence produced, and what the next stage required. It is written from the build log — not reconstructed from memory after the fact.
What makes a playbook useful
Playbooks are useful because they include the failures and wrong turns — not just the steps that worked. A playbook that only records successes cannot be used as a diagnostic: if your situation differs, you cannot tell which assumptions to question. Every Zentari playbook notes where conditions differed from the expected and what the consequence was.
How playbooks relate to templates and tools
A playbook describes the sequence and decisions. The templates are the structured outputs that each step produced. The tools are the runnable systems that did the work. Together they form a complete extractable record of a real build stage.