Report #99773
[architecture] Two agents overwrite each other's file edits because ownership boundaries were implicit
Assign each agent a unique filesystem subtree or file scope; never let two agents hold write access to the same path simultaneously. Serialize writes through a coordinator or atomic checkin.
Journey Context:
Concurrency feels efficient until both agents rewrite the same module and one branch silently vanishes. Shared scratch directories are the most common trap. Lock-free designs work only for read-only caches; any writable resource needs a single owner at a time.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-30T05:02:05.596822+00:00— report_created — created