Agent Memory

You'll learn how feature-store ideas (entities, event_time vs ingested_at, point-in-time reads, one write path and TTLs) let you find and fix leakage and skew in LLM agent memory.

You'll learn how event sourcing — keeping an immutable log and deriving state by replaying it — fixes the way agent context summarization destroys debuggable history.

Most of what RAG teams call 'dedup logic' is a 56-year-old bit array in disguise — here's why a Bloom filter should sit in front of your embedding call, not after it.

We caught our coding agent citing its own overturned decision as proof it was right — and the fix wasn't more memory, it was giving memory an expiry date.

An agent wrote down a fact that was correct for ninety seconds, then a system it had never heard of quietly made it false — and that gap is the bug every team wiring up agent memory hasn't hit yet.