Two agents, one file and an approved decision that disappeared
A rule I had approved vanished from a log where nothing is ever deleted, because two chats saved the same file and the last one to save won.
New to this topic? Start with World 1 of AI.
Part 4 of 6 of the series A different 7–1 every day.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
A different 7–1 every day. New here? Start with the introduction.
In July, a rule I had approved disappeared from a file where, by definition, nothing is ever deleted.
What happened?
I keep a log of lessons learned: every time a piece of work with AI agents teaches me something, the lesson goes into a file of its own. That file has one simple rule: entries are only ever added, never deleted.
At the end of July I approved an addition to one of the lessons. It was a practical rule: to list every file in a large folder on my computer, one of the agent’s tools stopped silently at two thousand files and handed over the list as if it were complete. The rule said which tool to use instead.
Two days later, the addition was gone. A chat needed to add another entry to the same log and, instead of adding it, rewrote the whole file from the version it had to hand, which didn’t yet include the addition. When it saved, its version was the one that stuck.
The same session brought a second warning. The copy of the file that the agent brought in from disk was less than half the size of the real file. No error, no message. A rewrite from that copy would have wiped out more than half of the log.
What was the score?
One approved decision, deleted without a trace. I only found out because I went looking for the rule and it wasn’t there. I rebuilt the lesson as a new entry, from what had been recorded of the session in which I had approved it.
Why wasn’t it bad luck?
Two processes, one resource and no coordination between them. Each chat worked well inside its own conversation, yet neither knew the other was also writing to the same file. Under those conditions, whoever saves last wins, every time.
Nor was it a one-off. On a single day in August, the same project piled up several successive status files, none of them marked as the current one, and one chat recorded as “to be fixed” items that another had already fixed and proved hours earlier.
Why did nobody see it coming?
Whoever deletes doesn’t know they deleted, and whoever lost only finds out when they go looking. The chat that rewrote the log did exactly what it had been asked to do, and the file was still valid, readable and looked complete.
What has to exist?
Every important document needs a single writer at a time, and everyone else has to know who that writer is.
In a log where nothing is ever deleted, the biggest risk turns out to be whoever writes in it.