Chapters & unlocks
The seven chapters, their dependencies, and the card states.
Most chapters are open from the start; the few with a real dependency stay locked until the work they depend on is done.
The dependency graph
| Chapter | Unlocks when |
|---|---|
| PRD | Always open |
| Design | Always open |
| Code | Always open |
| Docs | Code started |
| Deck | Code started |
| Token Launcher | PRD approved |
| CMS | Rolling out soon; activates with a Better i18n connection |
Only two gates remain: the Token Launcher waits on PRD approval, and Docs and Deck wait until you've started building in Code (your first Code chat turn). Design and Code are open from project creation — the approved spec is their best input, not their key. The Deploy action in the hub's top bar is always available.
The four states
Every card is in exactly one of these, and the treatment is identical across chapters so two cards in the same state always read the same:
| State | Means | Action |
|---|---|---|
| Approved | Finished and signed off | Open |
| In progress | Real content, not finished | Continue |
| Ready | Unlocked but untouched | Start |
| Locked | Waiting on an earlier chapter | - |
A locked card isn't clickable; its message tells you what to finish first ("Complete the PRD first", "Start Code first").
How status is decided
Each chapter computes its own status from real project state:
- PRD → approved when you've signed off the spec.
- Design → in progress once screens exist; approved when generation is complete.
- Code → in progress after your first build turn; approved when you sign the chapter off (building alone keeps it in progress).
- Docs → approved when every doc is current (none drifting or empty).
- Deck → in progress once slides exist.
- Token Launcher → in progress while a contract is drafted or compiled; approved once deployed.
- CMS → rolling out soon; once it ships, not activated until you connect Better i18n and activate, active after.