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.
More from coding & agent
- LinkedIn says a LangGraph hiring agent cut time-to-interview by 60% — LangChain · 2026-07-22
- Localmaxxing says it now tracks 3,500+ local AI runs across 444 model setups — LocalMaxxing · 2026-07-22
- AI Product Eval Challenge: Parallel System and Product Development Delays Stable Metrics — _ScottCondron · 2026-07-22
- Agent answered wrong on zero-click blog posts after skipping the CMS cross-check — philrox_ · 2026-07-22
- Reddit asks whether Plugsky is really unlimited for agentic coding — Riley0206 · 2026-07-22
- Sloop routes design specs to background coding agents for build-review-merge — clankers9197 · 2026-07-22