This maps to something I keep seeing too — orchestrators hand you correctness on state that lives inside the graph (reducers, channel semantics, wfh’s point above), but the moment the agents reach outside the graph to a repo, a row, or a file, you’re back in plain read-modify-write territory and you have to rebuild version-check / CAS / leasing at the app layer. The nastiest part is exactly what you said: the final state is syntactically fine, the diff looks reasonable, and one side’s work is just gone. Genuinely curious — in the cases you ran into (two agents editing the same repo / the same task list) how did you actually notice the silent overwrite? Was it a user complaint, a diff review, or did you catch it because one of the agents’ own checks started failing downstream?