A deeper dive into the architecture and philosophy of the InterBrain and my full conversation with David. Welcome to the subscriber companion to “Enter The InterBrain.”
In the main post, I walked through the InterBrain’s DreamSpace — the ontology, the workflow, the philosophy of knowledge weaving. Here I want to go deeper into what’s actually happening under the hood, because the engineering choices are as philosophically rich as the interface itself. This is also where I share the full deep-dive conversation with David, where we get hands-on with the beta and geek out about everything from Git sub-modules to digital shamanism.
What follows are some of the threads from that conversation that I found most fascinating — the technical architecture that makes the InterBrain’s vision possible, and a few insights that didn’t make it into the main post.
Galaxies Built on Git & Free Radicle Friends
David’s architecture for the InterBrain is visionary, and the engineering is equally practical. The astrally-inspired design is built on a foundation of open-source protocols.
To start with, every DreamNode is a Git repository. And Git, as David points out, is already a holonic system — software modules are holons, and Git’s sub-module feature lets you nest them recursively. In practice, this means that any DreamNode can contain other DreamNodes within it, like ideas nested inside larger ideas, and the whole structure stays organized and portable.
The InterBrain uses this to powerful effect. When I weave a DreamSong that references media from other DreamNodes, either made by me or by other Dreamers, the InterBrain automatically imports everything as Git sub-modules. The result is fully sovereign: I can hand a DreamNode to someone and it contains all the dependencies it needs to self-replicate. No broken links, no missing files, no dependency on a central server.
For the collaboration layer, the InterBrain uses Radicle — a decentralized, peer-to-peer alternative to GitHub. Each collaborator maintains their own completely sovereign branch of every DreamNode and DreamSong. There’s no forced consensus. If someone commits a change to a shared DreamNode, I see it in my inbox and I can preview, accept, or reject each commit individually. If I reject something, my Dreamer peer keeps their version. Coherence only emerges when the content resonates.
David calls this the Social Resonance Filter. If someone evolves a brilliant fork and everyone accepts the commit, it propagates through the social graph like a signal through a network — a kind of meritocratic broadcast. If it doesn’t resonate, it simply doesn’t spread. No algorithm decides, no central authority curates. The network self-organizes through trust, taste and resonance. Vibes as infrastructure FTW.
The Coherence Beacon: How Ideas Find Their People
This is where the InterBrain’s philosophy gets especially interesting. Git doesn’t normally track “super-modules” — that is, when a piece of code gets used in a larger context elsewhere. For software, that’s never been needed. But for knowledge weaving, it’s everything.
When someone in my Liminal Web uses a shared DreamNode as part of a larger DreamSong — a bigger game, a new project, a synthesis I haven’t seen yet — the InterBrain sends a Coherence Beacon, an invitation that says: “Hey, this thing we both know about is being used in something larger... Want to check it out?”
If I accept the offered artifact, I receive not just the new DreamSong, but all the puzzle pieces it contains that I don’t already hold, a new constellation. My horizon expands — but gently, because I already have at least one piece of shared context, and it comes from someone I trust.
What makes this different from a notification or a feed is that the Coherence Beacon isn’t an algorithm guessing what I might like — it’s a real topological connection in the knowledge graph. I share a piece. Someone I know used that piece we both care about in something bigger. The invitation is precise, contextual, and comes through my trust network.
David described the potential: “There could be movements spawning up, and no one would really know — they would all just feel something is really vibing here. But suddenly something like the GameStop miracle on steroids would be coming out of that. Not because we plan it, just because it happens.”
And here’s the design choice that makes it feel safe rather than overwhelming: you will only ever see peers that you consciously put in your Liminal Web. Even if millions of people are collaborating on the same DreamNode through chains of trust, you only see your people. The scale is invisible on purpose while the intimacy is preserved.
DreamTalk: Symbols as Communication Tools
One concept that emerged during the demo is the idea of DreamTalk — the symbol or thumbnail image that represents a DreamNode. This isn’t just decoration. David’s intention is that these symbols become invocable during live video calls. When Co-Pilot Mode is running and you’re in conversation, you can pull up a DreamNode’s symbol on screen to enhance what you’re explaining — like a visual aid that carries the full context of the idea behind it.
The question of what deserves its own DreamNode essentially becomes: what deserves a thumbnail? If a meme, image, or concept stands on its own — if it’s something you’d invoke in conversation to explain an idea — it earns its own node. If it’s just supporting material (a dozen photos from an experiment, say), it lives inside a parent DreamNode as context clutter until it’s ready to be “popped out” into sovereignty.
In future builds, David wants to make this completely fluid, offering users the ability to nest a piece of text or an image inside a DreamNode, then later promote it to its own sovereign node. The system handles the Git sub-module rewiring automatically without breaking anything. Structure grows organically, not from pre-planning.
SongBooks for Agentic Context
Every DreamNode contains a context document that defines what a DreamNode is — not just for humans, but for AI agents. I humbly offer the term SongBook to replace the current README nomenclature. This companion document like a metadata layer, although it’s more apt to call it a meta-context layer. This is where the evolution of the idea is tracked.
Thanks to the Co-Pilot transcription system, the context document doesn’t have to be meticulously written by hand. As you explain a concept across multiple conversations, the spoken-word data accumulates in the DreamNode’s SongBook, and AI can synthesize that into an increasingly rich SongBook. The spoken word populates the machine-readable context. You just talk, the context is recorded, and the agentic system learns can learn more deeply what a meme actually means.
One-Click DreamSong Publishing
A small but delightful feature: any DreamSong can be published as a standalone static website with a single click. The InterBrain uses GitHub Pages to generate a public URL that displays the DreamSong in the same visual format as the in-app experience — the same flowing narrative with embedded media. Anyone can view it, even without the InterBrain installed.
The trade-off is transparency — it creates a public GitHub repo, so sensitive material wouldn’t be appropriate. But for sharing ideas publicly, it’s a beautifully low-friction way to take a woven narrative from your private DreamSpace to the open web.
LLMs as Commit Mediators
One of the most pragmatic insights from our conversation was about the role of AI in making Git — historically a power-nerd tool — accessible to everyone. David’s position: you don’t need nerds anymore to use Git. LLMs can be the mediator.
The cultural patterns of good Git hygiene (small commits, meaningful messages, new files for new ideas rather than monolithic documents) don’t need to be learned by every user — they can be encoded into system prompts for AI agents that manage the DreamNode repos on your behalf. You interact with ideas. The AI handles the version control.
This is especially important for the collaboration layer, where accepting and rejecting commits from peers could become complex. David envisions AI summarizing what’s changed, flagging potential conflicts, and helping you make decisions about what to accept — all within the Social Resonance Filter framework. The goal is that the Git layer becomes invisible, while its sovereignty guarantees remain fully intact.
The Installation Is the First DreamNode
One last thing that struck me from the demo: the very first thing that happens when you install the InterBrain is that you receive the entire source code. The InterBrain plugin itself becomes the first DreamNode in your vault. You don’t download a binary from a server — you clone a Git repository that contains the tool you’re about to use.
This is philosophically coherent in a way that most software isn’t. The tool is its own first artifact. It’s open, inspectable, forkable. And because it’s a DreamNode, it connects you to every other person running the InterBrain. It’s the shared root of every Liminal Web — the one DreamNode that all Dreamers hold in common.
Learn how to install your own InterBrain DreamNode and support David’s work at Open Collective!
The full conversation covers all of this and more — including watching me fumble through my first DreamSong weave in real time, which is both instructive and entertaining. If you’re considering trying the beta, this video will give you a much better feel for the hands-on experience than any written description can.
Want to support the InterBrain? Visit Project Liminality on Open Collective. Want to try the beta? Reach out to David Rug through the Project Liminality YouTube channel.
