The memory problem
Ask Claude or ChatGPT to get you ready for tomorrow’s meeting and it goes looking — right then, in a few seconds, through whatever it can reach. KNET Brain is the memory it has been missing: built up a little every day, so the answer comes from two years of your work instead of this morning’s search.
Watch it come up short
the same question, twice
›help me prepare for my meeting with Acme tomorrow
!Answered from 4 days of a two-year relationship.
›help me prepare for my meeting with Acme tomorrow
✓Every call, thread and decision since day one.
the reading already happened · a little every day
What is actually happening
You ask them to prepare you for tomorrow’s meeting. They started five minutes ago. So they do the only thing they can: search your inbox for the client’s name, skim what comes back, and write you a summary.
It will be well written. It will sound assured. And it will be built out of whatever they happened to turn up in the time they had.
A brilliant researcher on their first morning — every single morning.
Three quiet failures
Three things happen in the background, and none of them look like an error.
Searching your inbox hands back a limited slice of what matched. For a busy mailbox that can be a couple of days’ worth. It has to stop somewhere — three months of email is more text than it can hold in its head at once.
Ask about a call and most note-takers return their own short recap rather than the transcript. The detail you actually remember saying is not in the room unless you insist on it.
If the transcript misheard your client’s name, that meeting does not exist as far as the search is concerned. And nothing tells you it was missed.
Nothing warns you. You get a confident, well-written answer built on a fraction of what you know — and it reads exactly like one built on all of it.
The objection everybody raises
It feels like it should be. Linking your inbox, your drive or a folder of documents to a project looks like handing the AI everything you know.
Every question sends it back through that doorway to start searching from scratch, with exactly the same limits as before. Nothing carries from Tuesday to Thursday. Nothing accumulates. Ask the same question next month and it does the same rushed search all over again.
A connection is a doorway,
not a memory.
A brain has already read everything, understood it, and written down what mattered — a little more each day, for as long as you have had it.
Side by side
Where the answer comes from
On its own — A quick search it runs the moment you ask
With a brain — Everything it has read and written down since you started
How far back it reaches
On its own — The first handful of results — often days, not years
With a brain — Every meeting, thread and decision, from day one
What it knows about a meeting
On its own — The note-taker’s short summary
With a brain — What was actually said, already digested into pages
What it remembers next week
On its own — Nothing. You start again
With a brain — All of it, plus whatever it learned in between
Who keeps it current
On its own — You, by re-explaining yourself every time
With a brain — It does. A little every day, on its own
The older idea
The idea is older than AI. People have kept second brains for years — in Obsidian, in Notion, in a shelf of notebooks. The principle is simple. Instead of one long diary, you keep one page per thing you care about: a page for a client, a page for a decision, a page for the problem that keeps coming back. Whenever one page mentions another, you join them.
Do that for a year and you no longer have notes. You have a map. And a map answers questions no single note can. What changed our mind on pricing. Everyone we know who is dealing with this. What we promised this client, and when.
a page for every client, decision and problem — and how they join up
So why does almost nobody have one?
Because keeping it up is a second job. The pattern is famous: you set it up over a weekend, feel brilliant for a fortnight, and then stop. Someone has to write every page, remember to join them up, and go back and correct the ones that have gone out of date. The upkeep grows faster than the payoff, and the whole thing goes quiet.
That is the part that has changed — and it is the only part that ever mattered.
What is different now
KNET Brain is a second brain your AI keeps for you. You give Claude one standing instruction — every day, go through my meetings and my email, and update my brain — and it does.
It reads them properly, not as a keyword search. It decides what is worth keeping, writes it as pages, and joins them to what is already there. It updates the page that exists rather than starting a rival one. When two sources disagree, it records the disagreement instead of quietly siding with the more recent.
You file nothing. You tag nothing. You do not decide the categories — it works them out as it goes.
Your own Claude subscription does the reading and the thinking. This is where what it learned is kept, so it is there tomorrow, and next year, and on your phone.
Before a meeting
“Get me ready for Thursday with Acme.” Not the last twenty-five emails — every conversation you have had with them, what was promised, what changed, what is still open.
The name you half remember
“Who was it that mentioned warehouse automation?” One passing remark, on a call, eighteen months ago. You had forgotten it. It had not.
The link you would never have made
On a pipeline call you rattle off ten companies. Each one becomes a page. Six months later one of them turns up in an unrelated conversation — and the two are already joined.
The AI did not get any cleverer. It finally has something to remember with.
Whose brain it is
This is the reason it is not simply a shared folder or a notes field in the CRM. Some of what is worth writing down is not for the whole company: your read on a negotiation, something said to you off the record, your own doubts about a deal. Everybody gets their own brain, and what goes in it stays in it.
Setup
Added like any other connector, in the app on your laptop or your phone. Nothing to install and nothing to run.
One standing instruction: every day, go through my meetings and my email, and update my brain. From then on it keeps itself.
Answers are drawn from everything at once, and they name the pages they came from — so you can check the claim rather than trust the tone.
Free, either way
These are the standing instructions you hand to Claude. One tells it to check your brain before it answers. The other tells it to write to your brain when something happens. Knowing when to do each is the hard half — and the reason most knowledge bases go quiet after a fortnight. Both are free, and yours whether or not you ever have an account here.
Tells Claude to look in your brain before it answers anything about your people, projects or decisions — and to say plainly when it finds nothing there, instead of falling back on a guess delivered in the same confident voice.
↓ knet-brain-consult.zipTurns a call, a thread or a decision made in a corridor into pages, linked as it goes. It updates what is already there rather than piling up near-duplicates, and when two sources disagree it records the disagreement instead of quietly picking a side.
↓ knet-brain-capture.zipNo lock-in
One link returns the whole brain as ordinary files — one page each, readable in any text editor. Open the folder in Obsidian and every link still works. Nothing in there needs us in order to be read, which is the only version of “no lock-in” worth anything.
By invitation
Accounts are opened by hand at the moment — there is no self-serve sign-up and this page will not pretend otherwise. Leave an address and we will come back to you.