The Feedback Loop Your Second Brain Is Missing

I spent months building my Obsidian vault. Wiki pages, journal entries, CRM notes — the whole Karpathy/Wolfe system. It looked great. Everything had a place. But something felt off. I was putting information in, but nothing ever came out. My second brain was a well-organized archive, not a thinking partner.

Then I came across a post by CyrilXBT that put words to what I was feeling: “A second brain that never talks back is not a second brain. It is a very organized way to forget things.” That hit hard. Because that’s exactly what I had built — a beautiful graveyard of good ideas.

The Five Layers

CyrilXBT’s architecture breaks down into five layers: Capture, Pipeline, Storage, Intelligence, and Return. Most people (myself included) nail the first three. You set up a web clipper, build a pipeline that routes raw notes into your vault, and organize everything into neat folders. That’s the easy part.

The hard part is layer four and five — having an AI that actually reads your vault, finds connections between notes you forgot you wrote, and then surfaces that knowledge back to you in a useful way. Without that return loop, you’re just collecting digital clutter with better labels.

What I Changed

I run Hermes Agent as my AI layer, and I realized it already had the tools to close the loop. I just wasn’t using them. The vault-first rule — where Hermes checks my wiki before answering — was already there. What was missing was the scheduled return: a daily or weekly synthesis that pulls insights from my vault and presents them back to me.

So I added it. A cron job that asks Hermes to scan recent journal entries, new wiki pages, and CRM updates, then compiles a morning brief. It’s not fancy. No vector databases, no RAG pipelines. Just structured Markdown and an agent that knows how to navigate it. As the Familiar project puts it: “You do not need RAG. You need structured Markdown + an agent that knows how to navigate it.”

The Real Test

The first morning brief surprised me. Hermes connected a note I’d written about DNS server configuration with a journal entry about network slowdowns — two things I never would have linked myself. That’s the whole point. A second brain should make connections you wouldn’t make on your own. If it’s just a fancy filing system, you’re leaving most of the value on the table.

Have you built a second brain? And more importantly — does it talk back to you?