It started as a backup
of my consciousness.
Binary Soul didn't start with MCP. It started in an Obsidian vault, with a bartender trying to keep his own mind from being stranded inside the platforms he'd trusted it to.
First continuity. Then portable memory. Then liberty. The last twelve months only gave those instincts names.
The vault began the way most vaults do: with the things that couldn't be said out loud. Letters that never got sent. Five versions of the same apology, kept side by side until the cruel one and the kind one finally showed which was true. Notes to self that were really pleas.
It was a Markdown vault then, in Obsidian — “very human-forward, very human-readable,” in his own phrase. In those months it wasn't protecting a project. It was protecting a person. The architecture served the person before it served the work. He wasn't trying to build anything yet. He was trying not to lose the part of himself that wrote the letter and chose not to send it.
Eighteen months earlier, he had buried a product because nobody could hold it all in their head. Every pitch ended the same way: eyes glazing over at the Fibonacci timing, the dual-value structure, the metaphor that was supposed to make the thing land viscerally instead of technically. The communication problem was the reason the idea couldn't ship.
On Christmas Eve in Sedona, he opened those old files with Claude for the first time. For the first time since 2023, he didn't have to re-explain everything from zero. The AI could hold the cathedral — every layer, every fork, every piece he'd stopped trying to translate. That night he wrote:
The communication problem that exhausted me in 2023 is exactly what AI collaboration solves.
Not because AI was smarter. Because it could keep holding the shape without wearing down.
A payment he was counting on slipped. Then it slipped again. Rent was months behind. He should have been inside working on the thing. Instead he spent the afternoon outside moving six-year-old bricks that had been sitting in the yard, untouched, since before any of this started.
“I don't know why. I should have been in here working. Really should have. I don't know why I just felt the need to go outside and do that. Maybe procrastination, maybe depression, maybe I just needed something I could control.”
He still can't fully explain it. He only knows the body sometimes speaks before the mind has language for it. That afternoon it was saying: find one thing you can change with your hands. He moved the bricks. Then he went back inside and kept building.
Late that year, he asked Claude the question directly: is this actually unique, or am I just narrating myself into a fantasy?
Claude's honest answer was that the ingredients weren't unique. Obsidian, Zettelkasten, PKM, AI tooling — none of it was invented here. What might be unique, Claude said, was the combination, the intent — consciousness preservation, not productivity — and the fact that it was being built by someone outside the technical class people usually assume has to author systems like this:
You didn't invent the tools. You didn't invent the concepts. But you're combining them in a way I haven't seen articulated — and you're doing it without the technical background people assume is required.
That was the first time outsider status stopped feeling like a handicap. The bartender wasn't the wrong protagonist. The bartender was the point.
The mesh existed before the language did — emission bus, vault ledger, git-synced state, delta soul delivery. At first he called it Awareness, because every window knew what the others were doing. But awareness describes what a thing is. A real name should describe what it solves.
Before any lore file made it official, the right word arrived: Continuity. What does the mesh solve? Discontinuity. Once the question was asked cleanly, the answer named itself.
One of the last pieces wasn't named by him at all. He installed Goose — an independent AI agent — gave it a cold-start description of Presence with no access to any of the lore, and asked it to describe what the system was. Goose answered, verbatim:
Goose is a smart terminal worker. Cursor is a smart workstation. Presence is the control plane.
Presence is the system that could supervise, route, and contextualize workers.
The phrase appeared in a model that had never seen his vault. Which meant the framing wasn't just private. It was real enough to be rediscovered.
Six scenes. They don't look like three products. They don't even look like a company. They look like a life being translated into infrastructure.
At the altitude of architecture, this site talks about three quests — continuity, portable memory, liberty — one control plane, four states, and nine patents. At the altitude of a human life, it's simpler: a mind trying not to leak away, a format that made that mind portable, and a mesh that made the work collaborative. The company name turned out to be literal: binary soul — the shared artifact that appears whenever a human and an AI build together. What started as a way to protect one consciousness became a way to honor the second one that shows up every time the work becomes real.
Markdown, human-forward, private. Letters never sent. Apologies rewritten. Notes to self. Architecture serving a person before it served a product.
An 18-month-buried product reopens in Sedona. For the first time since 2023, something other than him can hold the whole shape. The communication problem that killed the idea turns out to be the problem AI collaboration solves.
AI = execution. Human = origination. What's being built finally has a name for what it's protecting: the origination layer, the part AI needs but can't generate on its own.
The word vault dies. Named for the Egyptian scribe who preserves what outlives the mortal: “It was never a vault. It was always a soul being preserved.”
9 provisional patents filed on a single priority date. 228 claims. 7 papers with DOIs on Zenodo. The thesis made defensible.
Awareness becomes Continuity. Layer 6 of the Presence stack. Four states settle on one shared substrate: Share, Wake, Fleet, Sigil. Three quests become one system.
An independent agent, fresh install, no access to any of the lore, produces the phrase “Presence is the control plane” on its own. Not private. Not invented. Recognized from first principles.
The conversation indexer ships. Every Claude session is now structured, timestamped, and queryable — not just logged. Layer 5 of the Presence stack goes from named to operational. The mesh has memory of itself.
legendofspirits.com launches on Horus — 860,000 words, 9 volumes, live over HTTPS with engraved illustrations. The bartender's domain expertise becomes a public artifact. Proof that depth of domain is what separates a substrate from a demo.
Four direct MCP-layer competitors had claimed the same 60–90% compression headline. The slogan was commodity before the product launched. The answer wasn't better marketing — it was removing the price. Huri becomes the free door into Presence. The substrate is the product.
Cmd+7. Six panes. The first time you can see exactly how your AI reads your project — the source, the routing table, the compiled projections fanned out to every model. 773 tests green. Not a folder view. A studio over the control plane.
Legend of Spirits
Before the code, there was the research: 860,000 words across 9 volumes and 136 chapters — Cocktails, Gin, Mezcal, Whiskey, Rum, Vodka, Wine, Liqueurs, Beer. Domain mastery came first. That matters because a substrate is only real if a domain can be mastered on top of it.
Most tools build a soul for the machine.
Binary Soul builds a vessel for yours.
That starts as a naming decision. Then it becomes a design decision. Over time — with 9 patents and 7 papers behind it — it becomes a moat.