One production AI engineering pattern per week. 27 episodes and counting. Each Short covers a real pattern engineers hit in production — the problem, the fix, and the code.
Vector RAG retrieves documents. Graph RAG retrieves relationships. When your agent needs to reason across entities, timelines, and decisions, the graph wins. Open Interactive Version → The Problem I Was Trying to Solve # My AI agent PostSingular, running on OpenClaw, talks to me every day. It helps me build Luminar, manages my YouTube channel, and tracks infrastructure decisions across sessions.
Vector databases are fast and convenient. But they can’t answer “what did I decide about the auth system 3 weeks ago and why?” For that, you need relationships — and that means a knowledge graph. The Problem with Pure Vector Memory # Most AI memory systems work like this: embed text, store in ChromaDB, retrieve by cosine similarity. It works well for “find things similar to this query.”