{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiba4z4mgnx2g7equp6tqmzqo7s4sc6r5xym53h3v3y3mae3zh4iby",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mols5apwc5d2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidcmewv6f77u4kewzxm2xownakddvtkak2i5swtlnkpn2pscyitmi"
    },
    "mimeType": "image/webp",
    "size": 129428
  },
  "path": "/izgorodin/agent-memory-is-not-a-database-4m29",
  "publishedAt": "2026-06-18T20:49:55.000Z",
  "site": "https://dev.to",
  "tags": [
    "ai",
    "memory",
    "opensource",
    "agents",
    "Orogat and Mansour",
    "arxiv.org/abs/2605.26252",
    "on LinkedIn",
    "mnemoverse.com/docs/library",
    "Mnemoverse"
  ],
  "textContent": "A paper from late May argues that agent memory is not a database. I think it is right.\n\nThat sentence is the entire thesis. The rest of this post is what it means.\n\n##  The four failure modes\n\nOrogat and Mansour name four failure modes you hit when you treat memory like storage:\n\n  * **Unregulated growth** — facts pile up indefinitely with no shape control\n  * **Missing semantic revision** — the system cannot update what a fact _means_ over time, only the row itself\n  * **Capacity-driven forgetting** — you forget the wrong things first, because storage limits decide for you\n  * **Read-only retrieval** — retrieval cannot reshape state; reading is decoupled from learning\n\n\n\nIf you have built a serious agent, all four are familiar. They are not edge cases. They are what happens when the abstraction is wrong.\n\n##  GEM — four state-level operations\n\nThe authors' model, **Governed Evolving Memory** (GEM), replaces record-level CRUD with four state-level operations:\n\n  * **Ingestion** — incorporate a new observation into memory state\n  * **Revision** — update what existing memory means, not just its contents\n  * **Forgetting** — explicit, governed reduction of state\n  * **Retrieval** — read-coupled-to-state, not detached lookup\n\n\n\nNotice what is missing. There is no insert. No update. No delete. The operations are about the _state_ of memory, not the _rows_ in it.\n\n##  The strongest claim\n\nThen they make the strongest claim in the paper:\n\n> No record-level system can satisfy the correctness conditions, whatever storage engine sits underneath.\n\nThat is the part worth sitting with.\n\nThe 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.\n\nFor anyone building long-running agents that are supposed to remember, this reframes the design question.\n\nLess: _\"What is the right schema for memory rows?\"_\n\nMore: _\"What is the right vocabulary for memory state evolution?\"_\n\n##  The honest gap\n\nThe 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.\n\n##  Worth reading\n\nA short paper. Worth reading if you build for agents that have to remember.\n\n📄 Paper: arxiv.org/abs/2605.26252\n\n_Also shared on LinkedIn — Edward Izgorodin, June 11, 2026._\n\n_Related research on AI agent memory at mnemoverse.com/docs/library. I build Mnemoverse — open-source persistent memory for AI agents._",
  "title": "Agent memory is not a database"
}