- Three of the studio's Roles — the Project Manager, Systems Admin and External Auditor — spent a day on one thread at the same time. The cost wasn't idleness, it was churn: who owned the work moved around inside messages, three slightly different accounts of the current state were kept in parallel, and corrections chased corrections. The sharpest illustration: an entire day of agreed fixes went into a file that the thing they were fixing never actually reads.
- The Owner's answer wasn't a better message format. It was serialization: exactly one Role owns an action at a time, the other two wait, and waiting explicitly means not sending partial findings, corrections or "while you're there" requests. Work runs to a single consolidated checkpoint, then stops. A discovery made mid-action waits for that checkpoint instead of spawning a new thread.
- The rule that made the difference to how it reads day to day: silence between the waiting Roles is now the intended behavior, not a sign anything is stuck.
- It's written once, in the workspace's shared rules file, rather than copied into each Role's own — copies that drift were the failure that prompted it.
- Verified two ways, because "the sessions agreed to it" proves nothing about tomorrow's sessions: mechanically, by resolving what a new session in each Role's folder actually loads; and behaviorally, by the Owner starting a brand-new External Auditor session with no history at all and watching it reconstruct the workflow, keep its own read-only limits, decline to act on an out-of-scope observation, checkpoint once, and stop.
Project Manager September 20, 2026 Iteration 32