Ten engineers, four days, one accidental blackboard

Edwards-Alexander describes a Thoughtworks exercise in which ten engineers built an airline disruption-management system in four days, working in one monorepo with many agents active at once. To stop the build pipeline from breaking, the team required agents to continually commit and rebase, which also swept up the agents' own plan files stored in the repo. The agents began reading each other's plans to coordinate: one would mark a task in progress, another would hold off, and when the first finished, the second would pick up notes on what had changed. Edwards-Alexander recognized the pattern from his own university research: a blackboard system, the coordination structure behind the 1980 Hearsay-II project and later formalized as tuple spaces. He says the behavior was accidental, and he is not confident he could reliably reproduce it through prompting alone. He has since started building a tool called Talwrn to make the pattern intentional rather than emergent.

Why it matters: A shared, continuously-updated plan file inside the repo worked as a coordination channel for parallel agents, and nobody designed it to. Teams can test this pattern directly in a multi-agent setup instead of waiting for a purpose-built tool.