200apps · how we work

The Map

Two axes. The narrative axis — six phases of one continuous chain. The craft axis — thirteen Master Areas, in parallel. Every page belongs to a phase and a section. The map shows where they cross.

Phase → Areas

Four phases run per cycle, in sequence — Before → Shape → Build → After. Two phases are persistent: Why We Build sets the bet above any single cycle; Did We Serve? is the continuous relationship across cycles. The arrow from After back to Before is not a mistake — the chain closes and reopens at the model update.

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

Each role hub picks up the crafts in its column. The Teams section makes each role first-person.

Reading patterns

• End-to-end — phases Why We Build → Did We Serve? in sequence.
• By craft — open Master Areas and pick a section.
• By role — open Teams and pick the role you hold.
• By depth — pick a form from the home page (glance · skim · do · diagnose · internalise).
• By question — search (top-right). Local index, no external service.
• As an agent — fetch /llms-full.txt.