VECTOR SEARCH CAN'T TELL WHICH MEMORY IS CURRENT

Summary from the TLDR Dev newsletter

Plain vector retrieval returns the old preference and the new one, and passing stale context to an LLM leads to hallucinations and conflicting actions. Graph-aware retrieval fixes this at the database layer with typed edges linking each memory to the one it replaced, and lifecycle flags marking what's active. The agent gets a clean current state, and the full history stays intact.