Originally published on contextforge.dev .
Knowledge graph memory for AI coding assistants sounds like something you'd need a research team for. It isn't. It means your notes know about each other: this decision replaced that one, this bug depends on that config, these two rules contradict. That's the whole idea, and I learned why it matters from my own blog pipeline this morning.
The morning my notes didn't know about each other
I run a small n8n workflow that drafts a blog post twice a week. On November 13 I threw one of its drafts away because it repeated a post I'd published ten days earlier. I wrote down the fix: "add this topic to the blocked list." I saved that note. Done.
Today the same workflow wrote the same post again.
The fix was real. It just lived in a file that the workflow had stopped reading weeks before.…