302: The Whiteboard and the Shared Tree
Key question: How do agents share a board and a codebase without losing each other's work?
This Chapter's ACIs
| ACI | Name | Takeaway |
|---|---|---|
| ACI-059 | The Whiteboard | Four invariants: one writer per board, one appender and one clearer per inbox, a release condition on every hold, a stamp read from a clock. Boards are views generated from a store, and the writer rule is still a convention over --node. |
| ACI-060 | A Write Is Not a Delivery | Name the reader of every surface, say what must be acted on twice, and check a send by reading its target. |
| ACI-061 | One Checkout, One Index | A pathspec protects the committer, never the stager. Name the paths on both halves of every commit, and read the staged diff before it and the commit after it. |
| ACI-062 | Evidence Names a Moment | A result on a shared tree names a moment. Pin it to a commit and the tree it read, and reproduce a peer's red in a clean tree before attributing it. |
| ACI-063 | What a Worktree Isolates | Isolate contending nodes by worktree, not branch, keep the board on the shared ref, and list what the trees still share. |