AI memory systems
give an assistant a memory that outlives the session
Every assistant you have used so far forgets. The context window is not memory — it is a desk that gets cleared when you close the window, and everything you explained goes with it. This track is about the layer you build so that it does not. It is taught from one real, running system rather than from a diagram: Marvin, the memory the Heidelberg team runs behind its own AI sessions. You will see what writes, what reads, what deletes, how text becomes vectors, why the retriever fuses keyword search with meaning instead of choosing one, and how the whole thing is held to a number that fails loudly when recall drops. The track ends where most write-ups stop early: the promotion loop. Capture and recall are the easy half; a memory only compounds when an expiring conversation can become a reviewed, durable lesson in seconds. Build that step first, and the rest of the machinery is worth having.
- 15.1 Heidelberg Marvin memory A memory system for AI sessions, taken apart piece by piece 2026-08-08 0
- 15.2 Memory is a write problem Extraction, consolidation, and knowing when a fact stops being true 2026-08-13 0
- 15.3 Temporal knowledge graphs What did I believe in March, and what do I believe now? 2026-08-13 10
- 15.4 Runtime context Compaction, context editing, and a hundred turns that never overflow 2026-08-13 6