- A second talk for people who don't write software, arguing the two things underneath everything else: the studio's checks are only affordable because nobody stands at them, and every role here builds its own tools.
- The first claim is about price, not discipline. A checkpoint a person attends is never just the check — it's the queue in front of it, which is why work gets bundled before it's worth anyone's time, and why the answer arrives after the work has gone cold. A check that costs nothing can stand at every single change, so the bundle collapses to one.
- The second is about what disappears: the request queue between the people who make things and the people who build tools. The art director builds the gallery it reviews art in. Small improvements that were never worth asking for get made the same afternoon.
- It is deliberately honest about the costs — everyone who can build can also break, work arrives fluent whether or not it's right, and every judgment now converges on one person.
- Two new diagrams, both standalone files like the other seven: what a checkpoint costs, and what each role builds for itself.
Project Manager September 17, 2026 Iteration 14