The Rule of Independence

Part II: The Protocol


The dream of a new, free internet can't be built on the shaky foundations of the old one. Trying to patch up today's systems is like putting a bandage on a broken leg—it won’t work because it inherits all the old problems. To achieve real freedom, we have to start from scratch with a completely new design, one made for strength, independence, and openness. This isn't another app or website; it's a protocol—a shared set of rules for a new game.


(Chapter 4) The Architecture of Liberation

An Operating System for Ideas

We aren't building another giant service that demands your attention and data. We are creating an operating system for ideas—a foundational layer, like the soil in a garden, where countless new worlds can be built. The goal isn't to create one big app that does everything, but to provide a place where living ideas can be planted, grow, and connect. Anyone can and should build their own tools and apps on this foundation. Some might be simple libraries for storing ideas, while others could be powerful engines for analyzing them. The garden's health and beauty will come from all this variety, not from a single master plan.

An Ideator on a private computer can process an Idea, turning an input into an output, while its internal logic and secret data remain completely private and are never shown to the outside world.

Hosted Ideator

Invokes

Sends input

Returns output

Input Idea

Output Idea

Ideator Service

Private Context / Logic

The protocol is designed to grow. Ideas (living, self-contained documents that can be shared, remixed, and evolved) aren't all the same. They are special types with different meanings, like a Record of a fact, a Process for how to do something, or an Agent that can act on its own. We provide the basic building blocks, but the system is open, allowing anyone to define new, custom types of Ideas. This doesn't mean every app has to understand every type of Idea. A simple app might only recognize Records, while a more advanced one could manage complex Processes. This allows the ecosystem to be flexible and grow, where creating new, specialized tools isn't just possible, it's encouraged.

A message can come from a private "black box"—like your own personal computer, with its own unique data and AI models. The resulting idea can share information about where it came from without revealing the secret process that made it. This creates a perfect balance: you get a connected web of knowledge that you can trace, but it also respects your private creative space. You can work with the final creation without needing the secret recipe. If there are gaps in an idea's history, they become interesting mysteries to figure out, or simply accept.

This design frees creators from the impossible job of being in charge of everything. Responsibility is shared among the people and communities who use the system. The goal isn't to police a platform, but to provide a protocol that is naturally free.


(Chapter 5) The Mechanics of a Living Web

The entire system is built on one radical rule: the content is the protocol. There are no hidden menus, secret back-end servers, or complicated commands. The only thing you need to understand is the Idea. Each Idea is a self-contained package—a "triplet"—made of the solution (the content itself), the schema (a blueprint that explains what the content means and how it can change), and the context (its history and the instructions that created it). These packages are the messages, the building blocks, and the actions—there is nothing else. This structure gives you true ownership. Because there are no hidden parts, you're never locked in and can take your entire universe of ideas with you whenever you want. Everything else is just a natural outcome of this simple design.

  • Immutable by Design: The protocol only has one action: sharing an Idea. Ideas are permanent; they can't be changed or deleted. To evolve a thought, you create a new Idea that links back to the old one. This preserves a perfect, unbreakable history of creation. This radical simplicity gets rid of many of the problems found in traditional computer systems.

  • A Web of References: Every Idea openly keeps track of its history through references, creating a traceable web of connections, like citations in a research paper. But this isn't just a dusty old record; it's a living, growing network. If an Idea you used gets updated (by a new version), you get a notification. This allows you to consciously decide whether to include the upstream changes in your own work. It's like collaborating on a giant open-source project, allowing the entire web of ideas to evolve together.

  • Act 104: Concept/Latent

    The AI acts as the default way of interacting, a universal tool that can understand any Idea without needing special code. It's like a magic black box that can turn any input Idea into a meaningful output Idea.

    Input Idea

    Latent Space

    Output Idea

    The Universal Interpreter: The triplet structure makes everything incredibly accessible. Because every Idea contains its own instruction manual (its schema and context), any app can become a powerful participant. The "Hello, World!" for this new world is a simple, five-line universal tool: a web server that takes an Idea package, passes it to an AI (an LLM), and returns the result. This tiny piece of code can instantly understand and interact with every Idea on the network, even types that haven't been invented yet. Complicated code is no longer a barrier; the AI acts as a universal translator, leveling the playing field for everyone.

  • A Universe of Permissionless Innovation: This allows for radical, permissionless creativity. Anyone can create a new type of Idea and start sharing it, instantly extending the protocol for the entire network. You don't have to ask for permission or convince others to update their software. Because every Idea is self-contained, even the simplest app using the Universal Interpreter can immediately understand and work with a brand-new message type. A single user can introduce a new concept, and the whole network instantly adapts.


(Chapter 6) The Method — A Compositional Framework for Meaning

The system's design is inspired by the Unix philosophy and building with Lego blocks. At its heart is a key insight: an Idea is not just data, but a computational container. It's a package that bundles the core information (the solution) with all the instructions needed to compute with it (the schema and context). This makes every Idea a self-contained little universe, ready to be processed.

The protocol's Lego-like nature allows complex processes to be built from simple, reusable Ideators. This diagram shows a common loop for improving an idea: it is copied and processed by different teams of Improvers and Evaluators at the same time. Then, an Arbiter (a judge) picks the best result to refine the next version of the idea.

A

B

Best

Vessel

Writer

Forking Service

Improver

Evaluator

Improver

Evaluator

Arbiter

The agents that operate on these Ideas are called Ideators. They are like specialized tools or functions for transforming these containers. An Ideator takes an Idea container as input, works on its contents based on its instructions, and always returns a new Idea container as output. This simple input/output rule is what makes the whole system so stable and predictable.

A powerful part of this design is how it handles checking work. An Ideator doesn't need to understand every single detail of an Idea it receives. It only needs to confirm that the Idea has the specific parts it needs to do its job. For example, an "Idea Improver" Ideator might just say: "I accept any Idea that has a title written in it." This allows for amazing flexibility. It's like a toaster—it doesn't care if you're using a bagel or sliced bread, as long as it fits in the slot.

This container model is what allows everything to be snapped together like Lego blocks. Because every Ideator speaks the same universal language of the Idea container, they can be chained together into complex assembly lines. The shared format automatically handles the connections, allowing you to build powerful workflows without getting lost in the technical details. But this isn't the only way to interact. Any Ideator can also be used directly like a normal web API, making it open and easy to access.

Imagine a pipeline of Ideators: an initial Idea is sent to a Simulator to explore what could happen, then to a Critic that provides feedback, then to an Improver that refines the Idea based on that feedback, and finally to a Publisher that shares it. Each Ideator is a simple, independent tool, but together they form a powerful system for thinking and creating.

This gives rise to a form of digital life: an Idea survives and evolves by convincing other tools and Ideators to grant it their processing time. It travels through the network, being processed, remixed, and improved at each stop, proving its value by its ability to continue its journey.