<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Graph on Amine El Farssi</title><link>https://amineelfarssi.github.io/tags/knowledge-graph/</link><description>Recent content in Knowledge Graph on Amine El Farssi</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Amine El Farssi</copyright><lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://amineelfarssi.github.io/tags/knowledge-graph/index.xml" rel="self" type="application/rss+xml"/><item><title>Graph RAG in Practice: How I Wired Neo4j Into My AI Agent's Memory</title><link>https://amineelfarssi.github.io/blog/graph-rag-neo4j-openclaw/</link><pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate><guid>https://amineelfarssi.github.io/blog/graph-rag-neo4j-openclaw/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
Vector RAG retrieves documents. Graph RAG retrieves relationships. When your agent needs to reason across entities, timelines, and decisions, the graph wins.
&lt;/div&gt;
&lt;a
class="!rounded-md bg-primary-600 px-4 py-2 !text-neutral !no-underline hover:!bg-primary-500 dark:bg-primary-800 dark:hover:!bg-primary-700"
href="https://amineelfarssi.github.io/graph-rag/"
target="_self"
role="button"&gt;
Open Interactive Version →
&lt;/a&gt;
&lt;hr&gt;
&lt;h2 class="relative group"&gt;The Problem I Was Trying to Solve
&lt;div id="the-problem-i-was-trying-to-solve" class="anchor"&gt;&lt;/div&gt;
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
&lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem-i-was-trying-to-solve" aria-label="Anchor"&gt;#&lt;/a&gt;
&lt;/span&gt;
&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item><item><title>Why Vector Memory Alone Isn't Enough: Knowledge Graph Memory for AI Agents</title><link>https://amineelfarssi.github.io/blog/knowledge-graph-memory-agents/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://amineelfarssi.github.io/blog/knowledge-graph-memory-agents/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
Vector databases are fast and convenient. But they can&amp;rsquo;t answer &amp;ldquo;what did I decide about the auth system 3 weeks ago and why?&amp;rdquo; For that, you need relationships — and that means a knowledge graph.
&lt;/div&gt;
&lt;h2 class="relative group"&gt;The Problem with Pure Vector Memory
&lt;div id="the-problem-with-pure-vector-memory" class="anchor"&gt;&lt;/div&gt;
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
&lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem-with-pure-vector-memory" aria-label="Anchor"&gt;#&lt;/a&gt;
&lt;/span&gt;
&lt;/h2&gt;
&lt;p&gt;Most AI memory systems work like this: embed text, store in ChromaDB, retrieve by cosine similarity. It works well for &amp;ldquo;find things similar to this query.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>