The problem: legal AI agents process data that cannot be mixed
A litigation firm deploys an AI agent to help associates review discovery documents. The agent needs to remember which documents have been analyzed, which privilege log decisions were made, and what matters still need review. This is a legitimate use case — the agent should build context across sessions.
But the discovery documents contain privileged communications between attorneys and clients. When the same AI agent is deployed for a different matter, it must not retain any memory of the first matter. And when the client requests their file in discovery, every access to their data — including AI memory retrieval — must be logged in a way that survives attorney-client privilege scrutiny.
This is the core tension in legal AI memory: the same properties that make AI memory useful (persistent, cross-session, context-building) are the properties that create privilege exposure and compliance risk.
Contract AI agents (contract review, redline comparison, obligation tracking) face similar constraints. A contract agent working on multiple M&A deals cannot remember deal terms from Deal A when working on Deal B. An IP due diligence agent reviewing patent portfolios for Buyer A cannot surface knowledge from Buyer B's portfolio.
