The North Star

Maximal Computing Liquidity

Not an operating system but the toolkit that authors them, deploys them, and maintains them. Its output is bespoke systems, each one able to be as capable, as sovereign, as private as its maker wants. The liquidity is the point: anyone can author, mutate, share, and inhabit a whole computing world, not just the few who could before.

A Clan and a Space, the two units

A Clan is the coordination layer: a bounded group of machines and people, with shared networking, shared secrets, and shared rules, administered together as one. It is the trust domain that decides who is inside and binds their machines into a private whole. You belong to Clans; you author Spaces. A Space can be yours alone or shared across a Clan, and a Clan can run many Spaces between its members.

A Space is a flake: a complete, reproducible description of a whole system, and data that arrives with everything it needs to run. It might be a single webpage that brings its own browser engine along, a full desktop with other people inside, a game, or a whole immersive world; the Space does not care what it contains. You may enter it, usually through an isolated micro-VM, as a visitor passing through or a resident who stays; it can be private to you, shared with a Clan, or open to the world, and it is self-owned, licensed to you by no one and held above you by no one, ourselves included. The sea change is in how it is delivered: full-stack and self-contained, the runtime shipped with the thing. This is, in its way, a replacement for the Web. The browser stops being the one necessary client, and protocols stop needing a standards body to bless them, because reaching something becomes a matter of packaging rather than conformance. To enter is to build the flake and securely execute its entry point; that is all.

What the toolkit gives you

• A computer that is genuinely yours to keep. Ownership of your own machine and its whole configuration, bespoke and declarative, maintainable by you and yours indefinitely, on hardware you hold rather than rent, under no landlord and behind no lock you were not given the key to. The rest of this list stands on it.
• Author without code, rebuild without effort. Lay out a whole system on a canvas or by prompt; the exact description is written underneath, where you need never read it, and that description is the system, raised again from scratch byte for byte anywhere.
• Isolation you can presume. Enter a stranger's Space, hand someone your own as a sealed container, or cage an agent and its output, each in its own micro-VM, the boundary well tested enough to be assumed rather than fretted over.
• Encrypted by default. Disk, memory, and backups, all encrypted as a matter of course, never a setting you have to remember to switch on.
• A local model, not a pipe to someone's servers. Sandboxed AI that runs on your own machine and authors alongside you, inspectable and yours, with nothing leaving the device you did not send.
• State on your terms. Run a Space that keeps nothing between sessions, or one that remembers everything, or carry your state with you from one machine to the next; the choice is yours, per Space.
• Backups that handle themselves. Automated, self-hosted, and mutually mirrored across peers on the network, so your whole machine can be restored from a twelve-word passphrase alone, with no service to subscribe to and no one else holding your data.
• Networking that wires itself. The machines you choose connect to each other automatically over encrypted channels, indifferent to IP addresses and able to punch through any network between them, with no manual plumbing.
• Distribution no one owns. A decentralized, content-addressed package manager moves systems and their parts with no central registry to capture or compel, and no central bottleneck to throttle the pace at which agents mint and compose new code.
• Discovery without a gatekeeper. Find real services across the wider network through decentralized discovery anchored on a chain, with no index-owner in the middle.
• Spaces to share, or not. Inhabit one alone, open it to a Clan, or let several people convene in one running Space with no server between them.
• The trustless core, reached directly. No browser extension, no hosted gateway, no cloud sitting in the path between you and the chain, the way full-stack access was supposed to work and mostly has not.
• Your own settlement layer. Because a Clan already binds a group around shared state, it is the natural seat for a private, ephemeral rollup that settles its members' transactions and commits them to the chain as canon.
• Trust and value, rooted on-chain. A Space can anchor its root of trust in the chain, carry an identity between Spaces, and move value with no middleman, while communities pool their own nodes into infrastructure they hold in common.

None of this is obliged. Every capability is a flake you compose in or leave out; a sovereign laptop and a private room for a family's photographs, and nothing else, is a complete use of all this.

Its overall state

• Beneath everything, ownership in a key you hold, on a minimal kernel we are driving toward formal verification, small enough to one day be proven correct rather than merely trusted.
• Software is partly stock and partly flow: some of it kept and maintained, some already summoned on demand by the authoring layer.
• Usability is the work we are bringing to the forefront, so the liquidity reaches people who never had it.