How to use this playbook as a reader

Status: drafted · Time: 5 min · Audience: everyone Outcome: Know the fastest honest route through the playbook for your current starting point.

If you’re short on time

Do three things:

Read the Prologue in order.
Take the self-assessment in §0.10.
Start at the first belt whose boss fight you cannot already pass.

That last line is the trick. Belts are not reading levels. They are evidence levels. If you can already pass a boss fight, you probably do not need to sit through every module before it.

The honest path

The playbook is arranged as a climb, but you do not have to read every page linearly.

If you are new to software: read Part 0 — Foundation, then the Prologue, then White Belt. Foundation gives you the vocabulary; the Prologue gives you the map; White Belt gives you the first shipped artefact.

If you are a PM, designer, ops lead, or TPM with some technical exposure: skim Tech 101, read Ops 101 properly, then read the Prologue. Ops 101 is where you can start saving time before touching a repo.

If you are an engineer: skim Foundation for the vocabulary your non-engineer teammates will now use. Read the Prologue, then jump to the first belt that stretches you. Green and Black are where the deeper craft lives.

If you are a manager or team lead: read the Prologue, §0.9, Ops 101, and Appendix L — Certification. Your job is not to read on behalf of the team; your job is to create the conditions where the team can earn evidence.

The three reading modes

Use the playbook in one of three modes.

Learn mode. You are trying to understand a concept. Read the chapter, stop at “what you should carry forward,” and say the idea back in your own words.

Ship mode. You are trying to complete a quest or boss fight. Read only the pages that unblock the next action. The evidence matters more than completionism.

Reference mode. You know what you need and are coming back for a specific pattern. Use the Master Index, Appendix N, and the live HTML hub search surface. Do not reread the whole track.

The best readers switch modes deliberately. They do not mistake reading for progress.

How to treat links marked [coming]

A [coming] marker means the playbook knows the section belongs here but the chapter is not yet drafted. The marker is rare: the belts and Council layer are drafted, Appendix E is an intentional skeleton, and Appendix M is the only planned appendix still waiting on the full operational template. When you do see [coming], do not wait unless your current goal depends on it.

If the missing page is Appendix M or another deliberately marked scaffold, treat it as a signal about the shape of the curriculum, not a blocker. Use the current chapter’s summary until the full reference lands.

Treat [coming] as a visible scaffold, not a broken promise — the playbook prefers naming the gap to hiding it.

What you should carry into the next chapter

Start at the first belt whose boss fight you cannot already pass.
Use Learn mode for concepts, Ship mode for quests, Reference mode for lookups.
[coming] means visible scaffold, not a broken promise.
Reading is not the unit of progress. Evidence is.
The next chapter, §0.9 — How to use this playbook as a team lead, translates the same material into an adoption rhythm for a team.

Previous: ← 0.7 Operating Principles · Next: → 0.9 How to use this playbook as a team lead