Part 7 of 12 · 1 min read
How to build it so it holds up
- Prefer message passing or one-writer-per-field when agents have clear ownership; use a blackboard for append-only, commutative contributions.
- Make every write an operation (append, add, set-if-unset), not a full-state replacement.
- Version anything that is read-modify-write, and decide in advance what happens on conflict: retry, merge, or escalate.
- Give every message an id and make handlers idempotent; add sequence numbers when order matters.
- Bound retries and define the failure path (dead-letter queue, human).
- Show each agent a scoped view and let it fetch more by pointer.
- Log every state write and message with agent id, version and id, so a lost update is visible in a trace (Level 9).