302: The Whiteboard and the Shared Tree
How do agents share a board and a codebase without losing each other's work? A fleet coordinates through two shared surfaces: a whiteboard, where nodes keep their boards and send each other messages, and a checkout, where they commit their work. This chapter teaches the whiteboard as a set of invariants, kept in Intent as views generated from a store, and a write to it as something short of a delivery, since every surface needs a named reader. It then turns to the shared tree, where a scoped commit protects the committer but never the stager, a test result names a moment rather than a commit, and a worktree isolates source but not state. The exercises make the room a small fleet, so the collisions happen between the people in it.
Materials
This Chapter's Insights
- ACI-059: The Whiteboard
- ACI-060: A Write Is Not a Delivery
- ACI-061: One Checkout, One Index
- ACI-062: Evidence Names a Moment
- ACI-063: What a Worktree Isolates
Browse every insight on the course map.