You implement multi-agent memory for a public-sector casework system. Requirements include encryption, retention limits, session isolation between citizens, and purge on case closure. Which memory implementation approach is correct?
Select an answer to reveal the explanation.
Short Explanation
Memory is a regulated store, not a junk drawer. Isolate sessions per citizen, encrypt, retain only as long as policy requires, purge on closure, and gate what agents promote to long-term memory. Option C. Shared mega-thread (A) leaks across citizens. Forever retention (B) fails compliance. Public gist backups (D) are a data breach waiting to happen.
Full Explanation
Memory strategies must address security, compliance, lifecycle, storage, and session management. Option C covers isolation, encryption, retention/purge, and write governance.
Option A causes cross-session data leakage.
Option B violates minimization and retention principles.
Option D is an unacceptable exfiltration path.
Align memory TTLs with legal holds; support subject-access deletion workflows.
Exam tip: Long-term memory writes should be deliberate and policy-checked, not automatic dumps of full transcripts.