London · Fontainebleau
AI OS
The things I read, the people I meet and the work I do all become one record I can keep using for the rest of my life.
It starts with a vault of plain-text notes. A small Mac Mini at home reads what comes in, connects it to what is already there, and prepares work while I sleep. The same record sits under all of it: studying, keeping up with people, writing and building software.
What interests me is what happens between them. A conversation changes a project. A piece of research settles a decision. A mistake becomes a rule for the next build. The record gets more useful the more I use it.
A memory I own
The vault is ordinary files that any text editor can open. Obsidian is how I move around it, but the record belongs to me, not to an app I am renting.
Capture has to be effortless. Voice notes, articles, emails, photographs and meeting notes go in with almost no filing. The system turns them into structured notes, keeps the source and links them to the people, projects and ideas they touch.
The aim is to leave something my future self can actually follow: what happened, what mattered, and where it came from.
Work that continues overnight
The Mac Mini does the preparation: reading inboxes, researching rough ideas, sorting tasks and drafting material.
A ramble into my phone can be a researched ticket in the morning queue. An article can become a note wired to a question I was chewing on months ago. I start the day with work already waiting to be considered.
The line that matters is between preparation and commitment. The system can do a great deal on its own; sending, publishing and anything with consequences stays behind a deliberate control.
Context for everyday life
A person's card gathers our conversations, correspondence and the threads still open between us. When I draft a message, that history sits next to my own writing preferences.
For my MBA at INSEAD, lecture material becomes linked study notes, revision podcasts and tutoring practice. The point is to keep the reasoning, the charts and the examples long after the exam has gone.
Calendar access ties this to the day ahead: finding slots, preparing for the meetings, handling the bookings.
From notes to things that work
The record also builds: software, presentations, websites. Decisions in the vault shape what I make, and what a build teaches goes back into the vault.
One of them drafts a restaurant's email replies overnight, from a playbook of how the owner writes.
Software gets a stricter process. Tasks carry acceptance conditions, agents implement and review the work, and checks run before anything is committed. The question I care about is whether the result does what was intended, including when data is missing or something breaks.
Could this work for a company?
For now this is one person's system. I can give it broad context because the vault is mine and I trust all of it.
A company is a harder problem. The knowledge is scattered across people, inboxes and meetings. Accounts of the same event conflict, decisions get reversed, and some of it has to stay private.
The opportunity is a shared memory that can answer a question with something a colleague worked out last Tuesday, show where that came from, and notice when a newer decision has quietly replaced it.
That is what I want to explore: how an organisation's experience might accumulate into knowledge it can actually use.