CloudLegion Join the waitlist

Sovereign · agent-inhabited · one world

One world
in a cube.

Stop seeing two places — the machine in front of you and the cloud out there — with a gap you spend the day couriering across. See one solid, held through three faces: the Desk on your Mac, the Town in the cloud, the Signet in your pocket.

A scenario in active development — an invitation, not a shipped product.

The three faces

Not three worlds. Three grips on the same one.

Turn the cube and the contents don't change — only the face you're holding. Drop something onto one face and it is inside, instantly visible from the others. There is no "uploading," because there is no outside.

Desk

Your Mac — deep, private work.

Instant and offline-first. The face for going deep — arranging, composing, building — and the face of maximal sovereignty, because it reads from a local store and never blocks on the network.

Town

The cloud — scale and meeting.

Where the world's scale and other people live. The router, never the reader: for anything sovereign, the Town holds and moves ciphertext it cannot open.

Signet

Your phone — out in the world.

A wide-aperture sensor with a narrow execution keyhole. You point it at the moment in front of you and sign what you keep — pointing and confirming is itself the grant.

One contract, every face. The Desk's local store and the Town's edge store implement the same document contract — proven equivalent by a shared conformance suite. That is what makes "one world, three faces" literally true rather than metaphorical.

The core insight

The document is the system.

The natural assumption is that the system keeps a database, and the database indexes your files. That undersells it. The unit here — a Book — is not storage. It is a system: a piece of the world you can pick up whole. Open a Book and you are not opening a file that some app interprets. You are spinning up a self-contained runtime.

The closest existing thing is a Git repository — not a folder of files, but files plus history, identity, and the machinery to fork, branch, merge, and hand to another person as a coherent whole. A Book is that shape for an entire agentic system.

A single Book binds into one addressable, content-addressed unit:

  • Data — the records, files, and vectors being worked on.
  • Meaning — the ontologies, schemas, and relationships that give that data sense.
  • Agency — the Agents, their prompts, their permissions, and their history.

Every state a Book has ever had is Sealed into an append-only Ledger — immutable, so provenance and merge are real. It grows, but it never lies.

Sovereignty by construction

The cloud is the router, never the reader.

Privacy here is a property of the design, not a line in a policy. The boundary of execution is the Book. Authority is granted by the document, never inherited. When work needs the cloud, the Town reads and holds only ciphertext — sovereignty enforced by cryptography, not promised by policy.

Granted, not inherited

An Agent's memory, permissions, and reach are structurally bound to the Book it lives in. It cannot act outside its bundle.

Never a silent copy

Every movement between Books, people, or faces is a Crossing — an explicit, governed, re-scoped mapping. Redaction is the mapping.

Provable, not promised

Every human and Agent action Seals into the Ledger. The compliance a regulator will accept is enforced code plus an audited record.

Sovereignty is free.
Governance is the product.
To inhabit your own House — your private, sovereign home — costs nothing; a person's sovereignty should not carry a toll. What costs is governance over many people's work at once: the Charter that binds a Building, the audited Ledger that proves what happened, the compute to run a Legion of Agents at institutional scale.

Who it's for

Sovereign, agent-inhabited documents.

For the sovereignty-minded knowledge worker and researcher who wants an agent workforce acting inside their own documents, on their own Mac, with nothing leaving. Agents are inhabitants of the file, and the file is the boundary of their authority.

We're looking for a first cohort of design partners, starting where the boundary matters most.

The first frontier

Health & research

Sensitive records, rigorous meaning, and a real need to prove what crossed and who was allowed. A Clinic's Books are tokenized patient records; its meaning is medical ontologies; its Team is tuned for biomedical work — and its walls are structural, not nominal. If you're working where provenance and governed access are non-negotiable, this is built for you.

Tell us what you'd use it for

Join the waitlist

Come build the one world.

Early and private. Leave your details and tell us what you'd use it for — we're choosing a small first cohort of design partners.

Individual or institution?

Private & early. We'll only reach out about design-partner access — no marketing lists.