Skip to slide
23 / 40

CH 04 · How Memory Fails · 01/10

Read as one page

How Memory Fails

Memory failures compound instead of fading away. Drift, retrieval mismatches, stale or hallucinated facts, self-reinforcing errors, and poisoning follow.

10 slides · 6 min read

Contour map for How Memory Fails

In this chapter

  1. 01A map of the failure modes
  2. 02Drift: knowledge slowly deviating from the truth
  3. 03Retrieval failures: getting the wrong memories back
  4. 04Validity failures: wrong or outdated facts
  5. 05Self-reinforcing errors and over-generalization
  6. 06Environmental failure: contradiction handling
  7. 07Safety failures: poisoning and privacy
  8. 08The design tensions underneath
  9. 09Key takeaways

Memory makes agents more capable, but it also introduces a whole new class of bugs that do not exist in stateless systems. This chapter catalogs them, drawing on the failure modes in the "Practical Guide" and the more formal taxonomy in the SSGM paper. Almost all of these are failures of the manage phase from Chapter 1: things go wrong not when memory is written or read, but in how it is maintained over time.

A theme to hold onto: in a stateless system, a mistake affects one response and then disappears. In a system with evolving memory, a mistake can be stored, reinforced, and acted on for a long time. The SSGM paper puts it crisply: unlike static RAG, where an error is isolated to a single retrieval, errors in evolving memory are cumulative and persistent.

Finished this idea?

Your learning progress stays in this browser.