Agent memory needs ontology, write paths, and graph-based retrieval
Al_Grigor · x · 2026-07-22
A repost about designing unified memory for agents argues that retrieval is only one layer of the stack. The author says the hard part is the architecture around it, and proposes a four-layer design:
- Ontology: define entities, relationships, merge rules, and how facts change over time.
- Durable write path: separate pipelines for raw document ingestion and transforming documents into structured memory.
- Query / retrieval layer: map natural language to graph queries, expand to connected nodes, find top-K results, and rerank them.
- LLM Wiki / context packing: maintain an index with sources, entities, preferences, and facts, then pack retrieved subgraphs into context.
The diagram ties this to an MCP server with retrieval and ingestion tools such as NL query memory, deep search memory, ingest conversation/file/URL, plus a harness and ingestion pipeline. The overall message is that useful agent memory is a system design problem, not just GraphRAG retrieval.
Related event: Developers Debate the Real Challenges of AI Agent Memory(6 posts)→
More from coding & agent
- Goal-driven AI needs verifiable success signals, or it invents its own — daniel_mac8 · 2026-09-11
- Is inference latency becoming the biggest bottleneck for production AI agents? — Euphoric_Sea632 · 2026-09-11
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11