Teams & Organizations
What happens when two people edit the same memory?
Short answer
When two people change the same piece of information, the worst outcome is the silent overwrite: nobody knows a conflict happened. The safer habit is to replace without erasing, with author and date visible, to name a single version that counts as the reference, and to let a human decide. The AI can flag the contradiction but should not referee it, and no technique replaces a clear team rule.

On Tuesday, Sonia updates a project budget: 40,000 euros. On Wednesday, Karim, who has not seen the change, types in 45,000, copied from an old spreadsheet. On Thursday, someone asks the team’s AI, which answers with one of the two figures and never mentions the other. The story is made up, but most teams have lived some version of it.
The instinct is to look for a tool that “handles conflicts”. Our answer is less exciting: never overwrite, always replace and leave a trace, and know in advance who has the last word. A tool can help you see the conflict. It does not decide who is right.
Three ways two versions collide
Not all conflicts are alike, and they do not call for the same treatment.
Two versions of one fact. An amount, a delivery date, a contact name. One of them is probably wrong, or out of date, but nothing says which.
Two contradictory decisions. Sales promised a deadline, engineering settled on a different schedule. Here both versions may be legitimate within their own scope. This is no longer a typo, it is a disagreement, and it needs a conversation.
The silent overwrite. The second person replaces the first without knowing it, and the first version vanishes. This is the most dangerous case because it leaves no sign: everything looks consistent until the day somebody remembers a different number.
An example: the budget edited twice
Back to Sonia and Karim. In the “overwrite” version, Karim types 45,000 over Sonia’s figure. On Thursday the AI says 45,000. Nobody knows that 40,000 ever existed, or why. The client gets a wrong quote, and someone has to trace it back by hand.
In the “replace” version, both figures sit side by side, each with its author and its date. When you ask the memory, the gap is obvious, and the question becomes: which one counts? The project lead looks, calls Sonia, and learns that her number included a discount negotiated on Tuesday. She establishes 40,000 as the reference version. Karim’s figure is not erased: it stays in the history, marked as replaced, with the reason.
The technology did not settle anything. It made the disagreement visible, and a human made the call.
Replace, do not overwrite
Overwriting erases two things: the previous value and the fact that it ever existed. Replacing means putting the new version in place while keeping the old one reachable, along with what explains the change: who, when, why. We went through this mechanism for decisions in what happens to the old decision when a decision changes.
On the Nawame side, a new decision can replace an older position without erasing the fact that the older one existed. Depending on the information available, provenance can keep when something was recorded, where it came from, who or what created it, and whether it has been modified or replaced since. The export includes the history of replacements.
If you do not use a tool like this, the same discipline works by hand: a table with a “replaces” column and a “reason” column already goes a long way.
One version that counts
Keeping every version is not enough: you also need to know which one gets read by default. Otherwise both the AI and the humans pick at random from the history.
The simplest fix is to name a reference version for whatever must be authoritative: a budget, a business rule, a policy. That is the “reference” status: an item deliberately established as a lasting reference, with a life cycle. It can be corrected or replaced, but by a deliberate act, not by whoever typed last. The status describes the place of the information, not any claim that it could never be deleted.
This only works if you do not mix everything together. Each person’s personal notes stay private, and the shared memory receives only what was shared on purpose. We explain that boundary in why personal memory must not automatically become company memory. For how to structure a record with a status, an owner and a date, see our piece on company memory AI can actually use.
What the AI should do when it meets a contradiction
Faced with two versions, an AI has two bad options: pick one at random, or pick “the most recent”. The most recent one is not necessarily the right one (in our example, the older figure was). Found does not mean true, and a newer memory is not more reliable just for being newer. We dig into this in why found does not mean true.
The right behavior is to flag it. For example:
- Bad answer: “The budget is 45,000.”
- Good answer: “Two figures exist: 40,000 (Sonia, Tuesday) and 45,000 (Karim, Wednesday). I can’t tell which one counts. Who can decide?”
The second answer is less smooth and far more useful. It gives the human what they need to decide, and it reflects a principle we keep at Nawame: judgment and decisions stay with people.
Who can edit what
Many conflicts come from too many people being able to change everything. Even by hand, you can separate several levels: who reads, who proposes a change, who edits, who establishes the reference version. The more sensitive the level, the fewer the people.
Nawame offers organization spaces, teams and permissions to decide who can access what, and a key can be restricted to one organization or one folder. What is available for organizations is described on the Enterprise page. We are not describing a specific permission level here that the page does not mention: if your team rule needs one, check that it exists before relying on it.
Limits: tooling does not replace a team rule
We do not promise automatic conflict resolution, and we would advise you not to expect it from anyone. Two versions sitting side by side do not tell you which one is right. A rule that settles things on its own (the most recent wins, the longest wins) would just produce quieter mistakes.
Several things stay out of a tool’s reach:
- real disagreements, which need a discussion and sometimes a decision from above;
- the absence of a rule: if nobody decided who establishes the reference, nobody will;
- discipline: someone who edits without telling anyone is still a problem, even with a history;
- the quality of sources: a version replaced by an even worse one is still wrong, just better documented.
Finally, history grows over time. Keeping traces is useful as long as you can still read them, which is why dating them and reviewing what has been replaced now and then is worth the effort.
A team rule in five lines
Before picking any tool, write this down somewhere, even on half a page:
- Personal notes stay private; only what is shared on purpose enters the shared memory.
- We replace, we do not overwrite, and we write down the reason.
- For each sensitive topic (budget, schedule, business rule), one person establishes the reference version.
- When the AI or a colleague flags two versions, we deal with it within the week, with a name and a date.
- Once a month, we reread what has been replaced to check that the history is still readable.
To try this on a real topic, Nawame is free for up to 10 memories. And if your first worry is an AI mixing sources between two clients or two projects, read our piece on team memory without mixing sources.


