What a second brain is, and why anyone would want their own knowledge system

A second brain is an external memory that answers questions. That is how it differs from a folder of notes: it does not just store whatever you put into it, it connects one thing to another and can give you an answer together with its reasoning — where that answer comes from, and when the decision behind it was made.

The name is a metaphor and it can mislead. It is not about copying your head, or about no longer having to think. It is about a place where context survives: why something was done one way rather than another, what was known at the time, and what has changed since.

Why notes on their own are not enough

Almost everyone already has some notes. Hardly anyone goes back to them, and it is not out of laziness.

A note is written at one moment and turns out to be useful at another. You write down a decision from a meeting and at that point you know everything: who said it, what it concerned, what the alternative was. Three months later only the text itself remains, stripped of all that. The note is accurate and still useless, because you cannot make a decision from it.

The second problem is worse, because it is silent. Notes age without a trace. An entry reading “in progress” looks exactly the same on the day it was written and two years later, yet it means something different. An ordinary folder of files has no way to show that.

The third problem is the simplest: searching by keyword only finds what you remember is there. Anything that has slipped your mind you will never find, because it will not occur to you to look for it.

What a second brain adds on top of notes

Three things, all reducible to a single word: connections.

One thing has one place, and everything else points to it. A server, a client, a tool, a project: each is its own entity with its own card. A meeting note does not repeat that data, it links to the cards. When something changes, you fix it in one spot.

A decision is a record, not a memory. Every determination gets a date, a rationale, and what was rejected. That way, six months on, you can see not only what was decided but also on what grounds, so you know whether it still holds.

Knowledge accumulates instead of starting from zero. New material does not land next to the previous entries; it gets added to existing pages and tied to what is already there. After a year you do not have a thousand notes to sift through, only a few dozen pages that somebody has kept up to date in the meantime.

That “somebody” is often a language model today, and that is the part that has changed over the last two years. Organizing knowledge used to be work you had to do yourself, in the evening. Now it can be delegated, and the human role shifts from writing to deciding and checking.

How it looks in my own setup

I am not repeating anyone else’s promises here; I am describing the system I work in every day.

When I wrote this text, in August 2026, my vault held 1,057 notes. That number is not impressive and it is not the point. What matters more is the split: 192 notes are raw sources, which nobody edits, and 63 are synthesis pages, written and maintained on the basis of those sources. The rest is bookkeeping: projects, contacts, tools, documents, correspondence. The numbers grow every month, so treat them as a snapshot of that particular day, not as the current state.

That split is the whole point. Source material stays untouched, because six months from now I will want to check exactly what was written, not what I remember of it. Synthesis lives separately and can be rewritten freely, because you can always go back to the source.

Separately, I keep a journal: 461 entries between June 23 and August 26, 2026, so a little over two months. Each entry says what happened, what it touched and what conclusion it leaves behind. This is the part that surprises people seeing the system for the first time the most, because it looks like overkill. It earns its keep the first time someone asks “why is this built this way”, weeks later.

Client material does not live in the same place. Every project has its own, separate vault, and all that stays with me is a pointer: what the project is, what stage it is at, and where to find the rest. That is not a technical detail; it is the condition that makes it workable to serve several companies at once.

What a second brain does not do

Three things are worth saying outright, because without them the promise would be dishonest.

It does not think for you. The model suggests and organizes, but decisions stay with the person, and it is the person who is responsible for what the system claims. In my own vault, a statement about the state of things that nobody has measured is flagged as a hypothesis, and that is not decoration: a sentence that sounds credible can circulate across documents and gain authority through sheer repetition.

It does not run without a rhythm. A system that nothing has fed for a month stops being an answer to questions and becomes an archive. Upkeep costs less than building it, but it does not cost zero.

It is a system with one owner. What I describe here is the second brain of one person, or of a one-person company. A shared knowledge base for a team, with permissions and with resolving conflicting entries from several authors, is a different task, and I am not promising it in this text.

Who it makes sense for

Not for everyone, and not right away.

It makes sense when you work on many threads at once and come back to them weeks later: when running several projects, doing research, or running your own company, where you have to remember everything yourself anyway.

It makes sense when the cost of forgetting is real: when every so often it turns out something was already settled once, and now has to be settled again from scratch, because the record does not exist or cannot be found.

It does not make sense when you work on a single thread and the knowledge fits in your head and your inbox. Then the tool adds work rather than removing it.

What comes next in this series

In the coming installments I will describe the method the whole thing rests on (three layers, and why the model should write the synthesis rather than the sources), building a system like this from scratch, and adapting it to your own line of work. If you would rather work through this on your own materials than read about it, I run a workshop on building a second brain with AI — get in touch if you would like to talk about running it for your team.