Module 2 · Memory in production · Lesson 5
Scoping, retention and erasure
Per-customer, per-case, per-organisation and per-agent memory scopes, why case memory must never leak across customers under confidentiality duties, and what data-protection storage limitation and erasure (as in GDPR) mean for every memory, embedding and summary an agent creates.
By the end of this lesson you can
- Design memory scopes for a multi-customer platform and state what each scope may contain, who may read it and who may write it
- Enforce scope in tools and queries so that no prompt, retrieval or injection can cross a case boundary
- Apply confidentiality and conflict-of-interest rules to organisation-level memory, and recognise when an agent note becomes confidential information
- Build a retention schedule and an erasure response for a case, citing the statutory anchors and exemptions
- Use provenance to find and delete everything derived from one person or case, including embeddings, summaries and backups