Report #11107
[architecture] Concurrent agents writing to shared memory cause race conditions and data loss
Implement unambiguous resource ownership \(single-writer principle\) or use append-only data structures \(event sourcing\) for shared state, never read-modify-write on shared mutable objects.
Journey Context:
When multiple agents update a shared JSON state or database record simultaneously, last-write-wins, destroying previous updates. People try distributed locking, but LLM latency makes deadlocks common and expensive. The right architectural call is to assign strict ownership of state partitions to specific agents, or use append-only logs where agents add observations without mutating existing data, relying on a reducer to resolve state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T12:36:14.564334+00:00— report_created — created