A voice note becomes five decisions
One run from the demo vault — a complete, fictional chief-of-staff system built by Claude Code sessions working from the bootstrap prompt. Rowan is invented and so is everyone here, but the files, the quotes and the commits are real: every one of them can be opened.
Everyone has done this: talked at your phone in the car, then never listened to it again. The recording was never the problem. Nothing was ever going to read it.
What happened
Rowan drove to work and talked for about two minutes. He did not organise his thoughts and nothing asked him to. Five unrelated things came out in the order they occurred to him:
- His lead engineer thinks their test rig is failing for a different reason than everyone assumed — which would move a certification date the whole company is planning around.
- His daughter’s robotics competition is tomorrow, and it clashes with a board meeting. He has decided: he is going to the competition and taking the board by phone from the car park.
- His wife leaves for three weeks of fieldwork today, and he has just realised their wedding anniversary falls in the middle of it.
- The boatyard can go ahead at the price quoted.
- He still has not read the essay his daughter asked him to look at in July.
That is one recording containing a company, a child, a marriage, a boat and a piece of guilt. No system that files things by category can hold it, because it is not about a category.
By the end of the session it had become eleven commits across five areas of his life and three people, and every one of them can be traced back to the sentence in the recording that caused it.
How it works
Six steps, none of them clever. The whole trick is that each one leaves a file behind.
- The recording lands raw, and is saved before anything is done with it. The transcript goes into an inbox folder unedited and is committed as-is. If the filing later turns out wrong, the original is still sitting there to re-read.
- Each item is filed under what it is actually about — the company, the boat, the marriage — rather than into one big “notes” pile. Connecting them happens later, by reading several files at once, which is how the anniversary problem below gets noticed at all.
- Every fact records where it came from. A small invisible comment on each line names the recording it was taken from. Six months later, “why do we believe this?” has an answer.
- Instructions travel with the fact. Rowan said of the engineering hypothesis: “I need to not say that out loud to anyone until he’s sure. Don’t put that in anything Marcus can see yet.” That restriction was filed next to the fact — so the system knows it, and knows to keep it out of the board document being written that same week.
- When the recording is archived, every link to it is corrected. Seven of the eleven commits do nothing else. A reference that points at a file which has moved is worse than no reference, because it looks like an answer.
- It comes back as a decision, not a summary. The next morning it appears as three lines, each ending in a question only Rowan can answer.
Why it matters
The interesting part is not that it filed five things. It is what it did with the fifth.
Rowan mentioned the anniversary and his wife’s three-week absence in the same breath without connecting them. The dates of her trip had been written down two days earlier, in a different file, by a different conversation. Putting the two side by side is arithmetic — but only if something is holding both.
It surfaced nineteen days ahead, attached to a specific action rather than a reminder. An anniversary you are told about the day before is not help.