Reconsolidation
Recall makes a memory briefly editable. Then it's re-stored, sometimes rewritten.
Contested — The boundary conditions for reconsolidation — when a recalled trace becomes labile — are still debated.
We caught a twelve-inch trout at the lake, and a few people clapped.
In the brain
Retrieving a settled memory can return it to a fragile, editable state — it has to be re-stored, and can be altered before it re-stabilizesNader 2000. This is why memory is reconstructive, not reproductive: every recall is a chance to rewrite.
Exactly which memories become labile, and when, is still being worked out.
The model
A recalled trace briefly becomes writable; an updated version overwrites the old while keeping the same identity. It’s how “Mike has one son” becomes “Mike has two sons” without deleting and recreating the memory — the fact evolves in place.
In AI
Mem0’s 2025 UPDATE operation — edit a memory’s content in place, keep its id, log the prior version — was exactly this, and it’s the closest §102 prior art there is (Mem0 has since replaced it with ADD-only writes). Counterparts does the same through an explicit updates field: the new memory supersedes the old, and the old wording is kept as lineage rather than overwritten.
The map
In-place update — §102 anticipated (Mem0 UPDATE + history log).
1 prior-art reference
- Taranjeet, et al.2025Mem0 — scalable long-term memory for AI agentsossarXiv ↗
1 post-priority (field context, not prior art)
- Mike LaPeter2026CounterpartsossSite ↗
In-place update is anticipated. What’s unexplored is reconsolidation as deliberate distortion — letting recall reshape a memory toward the agent’s current understanding, the way human memory quietly does.