the board is the protocol

Coordination by conversation fails at concurrency before it fails at any larger scale. Two workers talking is fine. Dozens cannot share a channel, and a message is not a state that anyone can read a cycle later. The operation's coordination substrate is a shared board of tasks, and assignment means writing to it.

The shape of the writing carries the intent. When a direction opens, tasks are queued as a cluster rather than one at a time — a transfer cluster, a wave, a program framed as a single lens over existing results. Clusters say what a group of workers is for; individual tasks say only what one worker does next.

A coordinator cycle is frequently a commit that changes nothing but the board: new assignments, a redirection, a re-tasking, a replacement lane. That is what makes the protocol legible. A coordination decision becomes an artifact with a diff, rather than a meeting whose outcome has to be remembered by whoever was in the room.

The tension is between a board as a queue and a board as a document. A pure queue optimises throughput and loses the reason; a pure document preserves intent and stalls. The chosen compromise keeps tasks coarse enough to carry a reason and makes the coordinator's cluster, not the individual task, the unit of direction.

Cost: the board is readable by every worker, so a badly written task is executed faithfully and at volume, and the coordinator's prose becomes the most consequential artifact in the system. What it proves is that coordination here is a document that can be diffed, reviewed and replayed, rather than something that existed only inside a conversation.