In this analysis
Retrieval changes which evidence is available for a request; adaptation changes the model that interprets it. Their success criteria should remain distinct.
A longer context, a searchable archive and a model that changes its weights can all be called memory. The October sleep-framework explanation is a useful occasion to ask why that shared word hides different engineering promises.
The dated path
-
2025-06-12: Self-Adapting Language Models.
-
2025-12-31: Nested Learning: The Illusion of Deep Learning Architectures.
-
2026-10-27: Google explains the sleep framework for continual learning.
The distinction that earlier systems made unavoidable
Imagine an assistant that needs a newly published equipment specification. Providing the document at request time makes the source visible and allows the answer to refer back to it. That is a different objective from teaching a model a reusable reasoning procedure. Our retrospective interpretation is that persistent learning became compelling where repeating relevant material in every prompt was an awkward substitute for acquiring a capability, not merely where an archive contained a new fact.
A capability is more than an answer retained
A model that reproduces a recently seen answer has demonstrated recall under particular conditions. To argue that it learned a method, evaluate new examples that require the same underlying transformation but contain different surface details. Retrieval may still provide useful evidence for those examples. The mechanisms can cooperate while addressing separate problems: access to current information and a durable change in how information is processed. Confusing them makes both product claims and experiment design less precise.
A discriminating counterfactual
Hold the base model fixed and supply the necessary source material through retrieval. Then compare that system with an adapted model that receives equivalent evidence. If the adapted version improves on genuinely new instances, the update may be doing more than replacing a document lookup. If the advantage disappears when evidence access is matched, the result points toward information availability instead. Neither outcome is a failure of research; each locates the source of the benefit more accurately.
What infrastructure should keep separate
A retrieval record can often be attributed to a source document, whereas a parameter update requires its own lineage and evaluation record. Deleting or revising an external document and reversing a learned update are different operations. This makes lifecycle management central to any combined architecture. The research direction does not establish that one approach has made the other obsolete. For a provider, the useful consequence is to describe evidence access, model identity and learning transitions separately, so a request can be understood without guessing which meaning of memory applied. When a source is corrected, the system should also expose which form of retained state needs revision, making the correction path inspectable rather than implicit.
Technical background
Related engineering context: Retrieval architecture; Long-context constraints.