03 / Hardware · Analysis
Agent memory course separates source records from summaries
A DEV post recommends linking derived representations to source versions and deciding how to handle them when the source changes.

Oracle and DeepLearning.AI launched an agent memory course for AI developers, DEV reported on 11 Nov.
The DEV post described persistent memory, information retained over time, as the authoritative record. It classified summaries as representations derived from that record. This distinction underpins its advice to link each derived representation to a source version.
The post identified errors caused by mixing the authoritative record with techniques that optimise retrieval. Its focus was the distinction between source material and derived representations, rather than how memory is stored.
Source versions anchor derived representations
The DEV post classified cached context, as well as summaries, as derived representations. It distinguished the role of persistent memory from that of representations processed from it.
The post recommended linking each derived representation to the version of the source from which it was created. It also introduced a companion notebook for practical exercises.
Handling changes to the source
The DEV post recommended deciding how derived representations should be handled when their source changes. It named rebuilding, expiring and retaining them as options.
The design scope set out in the post extended from creating derived representations to handling them after a source change. Deciding what an agent remembers was therefore only part of the task: the design also needed to specify what happens to those representations when the underlying record changes.