Part 12 of 15 · 2 min read
Mistakes that turn memory into a liability
- Storing every kind of thing the same way. Symptom: corrected facts sit beside stale ones, or a decision gets silently edited. Cause: no update rule distinguishes a fact from an episode from a procedure. Fix: give each kind its own rule -- replace, append-only, versioned.
- Letting any source write to memory. Symptom: a web page or tool result becomes a permanent, wrong "fact" about the user. Cause: no write gate checks where a proposal came from before writing it. Fix: only trusted sources (user, system) write directly; everything else goes to quarantine for review.
- Treating a soft delete as forgetting. Symptom: a user asks to be forgotten, and their data is still recoverable from the database file. Cause: the delete only flipped a flag, or left copies in summaries, or never overwrote the freed disk space. Fix: hard delete every version, scrub every copy, and turn on secure delete -- then verify by scanning the file's actual bytes.
- Assuming the extractor caught what the user said. Symptom: a user corrects a fact in different words than expected, and the agent keeps answering with the old value. Cause: extraction only recognises a fixed set of phrasings. Fix: measure extraction recall on paraphrases, and keep a searchable raw log as the fallback.
- Replaying the whole history instead of storing it. Symptom: cost per session grows without bound, and stale values keep resurfacing once the replay window is large enough to include them. Fix: store facts, episodes and procedures with their own update rules, and reserve replay for the rare case extraction cannot handle.
- Trusting the label on a source instead of its content. Symptom: a user pastes an attacker's text into the chat, and because the turn's source is labelled "user" it writes straight to memory. Cause: the gate can only check the source label, not what the text actually says or where it originally came from. Fix: there is no code-only fix -- this is why a model that can be fooled by pasted text remains the weak point, and why review steps matter for anything sensitive.