Four agents wrote extracted contract facts to the same provisions.md page. The problem was not merely a model misunderstanding a provision: one agent saved a table after another had already modified it, and the later write overwrote material. The final answer consequently lacked facts that the team had encountered earlier. Source-owned pages plus verbatim…
Inspect the ClaimsCase · DiggingBeagle record
Concurrent agent memory edits lost 16 of 57 contract facts
Four agents overwrote a shared memory table during contract summary work.
Public disclosure: Nov 6, 2026
Anthropic internal multi-agent contract reading and memory-wiki experiment, not a field breach.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- not established
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- BY AI
Basis and provenance
Anthropic directly reported graded facts and the comparison of shared and source-owned files in a controlled multi-agent workflow, not hostile exploitation. An impact band remains unassigned because the available evidence does not establish a comparable severity score or verified numerical loss for this assessment.
Assessed Nov 8, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-ANTHROPIC-AGENT-MEMORY-LOST-FACTS-01 · Anthropic: components of agent memory
At a glance
A shared memory file is a concurrency surface. More model capacity does not restore facts that a later writer destroyed.
Read the implicationsSource-owned pages plus verbatim terms and feedback recovered the examined facts in this selected task. The experiment does not establish which database transaction, lock or merge technique is optimal in production, and it says nothing about resistance to malicious memory poisoning.
Limits and uncertaintyFull account
Four agents wrote extracted contract facts to the same provisions.md page. The problem was not merely a model misunderstanding a provision: one agent saved a table after another had already modified it, and the later write overwrote material. The final answer consequently lacked facts that the team had encountered earlier.
Source-owned pages plus verbatim terms and feedback recovered the examined facts in this selected task. The experiment does not establish which database transaction, lock or merge technique is optimal in production, and it says nothing about resistance to malicious memory poisoning.
The missing facts were not primarily a model failure to understand contract language. Several workers saved to one provisions.md file, and later writes erased facts extracted by other workers. In the reported experiment, the downstream brief carried 41 of 57 graded facts; switching to one source-owned page per contract and copying provisions verbatim raised this to 57 of 57. A versioned, per-source memory record is therefore a different control from asking the same agents to summarize more carefully.
Mechanism and trust boundary
- 01
Have multiple agents edit one shared summary artifact.
- 02
A later write replaces another agent’s extracted facts.
- 03
Generate a brief from the incomplete wiki and compare with source documents.
Claims & evidence
CLM-ANTHROPIC-AGENT-MEMORY-LOST-FACTS-01In Anthropic’s four-agent contract experiment, shared writes left 41 of 57 graded facts in the downstream brief, while separate source-owned pages preserved 57 of 57.supported
Basis: reported finding
- supportsAnthropic: components of agent memoryprimary disclosure
Four agents sharing provisions.md; before and after figure on lost facts
Implications
A shared memory file is a concurrency surface. More model capacity does not restore facts that a later writer destroyed.
Controls and mitigations
- Assign writes to source-owned pages or apply transactional merges with source citations and conflict checks.
Unknowns and contradictions
- Source-owned pages plus verbatim terms and feedback recovered the examined facts in this selected task. The experiment does not establish which database transaction, lock or merge technique is optimal in production, and it says nothing about resistance to malicious memory poisoning.
Sources and citation
Material revision history
- Nov 8, 2026 · Canonical change recorded · new in release · revision 229