Module 2 · Memory in production · Lesson 7
Shared state and memory poisoning
How a fleet of per-step agents should share one case's state (typed records, field-level write authority, compare-and-set and an event log rather than free-text memory), and how attackers turn memory into a persistent injection channel, with the defences that work.
By the end of this lesson you can
- Explain why structured, owned state beats shared free-text memory for a fleet of agents on one case
- Implement field-level write authority and compare-and-set updates on a shared case record
- Describe how memory poisoning differs from one-off prompt injection, using published attacks
- Trace an attack in which an injected document plants a memory that later drives a harmful action
- Design layered defences for memory writes and reads, and say what each one stops