Report #24461
[architecture] Two agents attempting to modify the same external resource simultaneously, causing dual-write conflicts
Assign unambiguous, exclusive ownership of external resources \(APIs, databases, files\) to exactly one agent, making all other agents request changes via the owning agent's API.
Journey Context:
If Agent A and Agent B both have credentials and logic to update a user record, they will inevitably overwrite each other's changes or deadlock. By applying the Single Responsibility Principle to resource ownership, the owning agent serializes writes and maintains invariants. LLMs struggle to handle Optimistic Concurrency Control \(409 Conflict retries\) gracefully.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:28:16.924897+00:00— report_created — created