Agent memory is not a database

Edward Izgorodin — Thu, 18 Jun 2026 20:49:55 +0000

A paper from late May argues that agent memory is not a database. I think it is right.

That sentence is the entire thesis. The rest of this post is what it means.

The four failure modes

Orogat and Mansour name four failure modes you hit when you treat memory like storage:

Unregulated growth — facts pile up indefinitely with no shape control
Missing semantic revision — the system cannot update what a fact means over time, only the row itself
Capacity-driven forgetting — you forget the wrong things first, because storage limits decide for you
Read-only retrieval — retrieval cannot reshape state; reading is decoupled from learning

If you have built a serious agent, all four are familiar. They are not edge cases. They are what happens when the abstraction is wrong.

GEM — four state-level operations

The authors' model, Governed Evolving Memory (GEM), replaces record-level CRUD with four state-level operations:

Ingestion — incorporate a new observation into memory state
Revision — update what existing memory means, not just its contents
Forgetting — explicit, governed reduction of state
Retrieval — read-coupled-to-state, not detached lookup

Notice what is missing. There is no insert. No update. No delete. The operations are about the state of memory, not the rows in it.

The strongest claim

Then they make the strongest claim in the paper:

No record-level system can satisfy the correctness conditions, whatever storage engine sits underneath.

That is the part worth sitting with.

The claim is not that databases are slow. It is that the abstraction is wrong. Correctness lives in how memory state evolves over time, not in any single record.

For anyone building long-running agents that are supposed to remember, this reframes the design question.

Less: "What is the right schema for memory rows?"

More: "What is the right vocabulary for memory state evolution?"

The honest gap

The prototype runs on a property graph, and the authors are honest about the gap: state-level revision and forgetting are expensive to do properly. Native engine work is still ahead.

Worth reading

A short paper. Worth reading if you build for agents that have to remember.

📄 Paper: arxiv.org/abs/2605.26252

Also shared on LinkedIn — Edward Izgorodin, June 11, 2026.