200apps · how we work

The Map

Two axes. The narrative axis — five volumes, in sequence. The craft axis — thirteen Master Areas, in parallel. Every page belongs to a volume and a section. The map shows where they cross.

Volume → Phase → Areas

The arrow from V to II is not a mistake. The chain closes — and reopens — at the model update. Volume V's last act is an input to the next cycle's Volume II.

The chain levels

Defects, gaps, and incidents trace to a level in the chain. Postmortems and the model update look for which level produced the gap — not which person. This is the structural-fix discipline that holds the whole thing together.

A bug filed today often has its root in a story written six weeks ago. A story written six weeks ago often has its root in a brief that was never witnessed. A brief that was never witnessed has its root in an initiative that was named without a person attached.

Tracing a defect to a level is not blame. It is the model update.

Owner → craft index

Reading patterns

• End-to-end — Volumes I → V in sequence.
• By craft — open Master Areas and pick a section.
• By role — pick your owner above and follow the crafts.
• By question — search (top-right). Local index, no external service.
• As an agent — fetch /llms-full.txt.