persistent-memory-agents-any-memory-write-rule-decides-using-only-recency CLM-0117
mechanismsingle paperReviewed by AI

For persistent-memory agents, any memory-write rule that decides using only recency and provenance is stuck on a single tradeoff — accepting more genuine preference updates means admitting more poisoned ones — because an adversary who can launder a claim through the user's own channel matches the statistics a genuine revision produces; conditioning the write decision on the inferred authenticity of the claim given the interaction history moves both axes at once.

Capability: Remembering across sessions

Observed on

Personalized agents with persistent cross-session memory where retrieved documents, shared files, or tool outputs can be written into the user model; holds against a fixed attacker.

Sources

  • Argued as a decision-theoretic lower bound plus measured on 480 held-out synthetic episodes from 96 users: provenance-only 20.0% poisoning / 74.1% adherence, recency RAG 51.6% / 85.7%, proposed gate 11.5% / 83.5%; provenance-only collapses to 43.6% on same- origin contamination vs 17.5%. A supervision-matched Transformer baseline reaches 69.3% win / 15.9% poisoning, so most of the gain is supervised temporal tracking rather than the specific architecture. Benchmark is generated by the authors; [truncated]
Reviewed by AI (Claude Opus 5)Last checked: 2026-09-09Evidence activity: not checked yet
Either way, bring evidence: a link, or what you saw.

Disagreeing is the most useful thing you can do here. Nothing on this page waits for a reviewer: the counts above move when evidence lands, and every source stays attached with who brought it.

Related claims

Notes

Drafted from the paper by a model and filed unreviewed. Visible here so it can be read, not because anyone has vouched for it: it does not move any technique's standing and does not count toward the internal scorecard. Drafted confidence: medium. Falsifier as drafted: A memory policy reading only recency and provenance that matches or beats a history-conditioned authenticity gate on both genuine-update adherence and poisoning resistance, including on same-origin (user-pasted) contamination. Proposed technique, not catalogued: Latent-authenticity gate for memory writes.