0k.computer

You should have a computer of your own.

That’s why we’re building instruments for thought on a foundation of collaborative, malleable computing — so you and the circles you move in can have just the functionality you need in your life, without paying subscription fees.

0k.computer is a portable layer that sits on top of the hardware you already own — and could, in time, become part of an operating system itself. What we build on it stands in the tools for thought lineage: literate programming, dynamic media, AI-assisted learning about the things that matter to you. And it carries a methodology of creation — shape your software as you see fit, combining bits and pieces of various applications into something that works for your context: you set the direction, your AI does the heavy lifting (the necessary-but-uninteresting delegated to it completely), and what you make is yours to share and to work on with others.

No tracker, no third party — this form posts to the machine serving this page and lands in a file we read ourselves.

The methodology of creation

— the one we used to create 0k.computer itself.

How an idea becomes a thing you keep

David Lynch said ideas are like fish — stay in the shallows and you catch the little ones; go deeper and you catch the big ones. Desire is the bait on the hook. What the hook pulls up, the methodology carries the rest of the way.

The catch is encoded as a seed, so it can gather context instead of fleeing; the seed sharpens into intents — actions small enough to take. Work worth repeating is kept as a gene — re-expressible as the world moves, so when the underlying technology shifts or a stronger AI model arrives, the gene is expressed anew instead of settled decisions being rehashed. A session does the work and leaves its whole run on the graph, so nothing is opaque. What lands is an artifact, traceable back to the want that started it — and what proves itself is curated into a bundle, and shipped:

Desire Seed Intent Gene Session Artifact x0k — the bundle
arises from your life experience “talk with my friends — privately” “my files, on every device” “AI that works for me, on my machines”
encoded — named, with appetite group-messenger — planted distributed-files — planted agent-runtime — planted
a potential action, yours or an agent’s a compose bar posting into the live store bytes on demand, across machines start an agent from a message
kept as re-expressible form messenger-compose.md, a literate doc files-surface.md, a literate doc in-app-agent-sessions.md
the expression — work happens an agent expressed it, on the graph expressed across two machines the runtime built pieces of itself
what lands, traceable to the desire the compose surface — it ran here the files surface, in the pilot provable deliverables, in your chat
the streams converge — a shippable whole ships with the messenger in it ships with the library in it ships with your agents in it

The first offering

What we ship first is x0k: the malleable runtime built on a frozen substrate, and, on top of it, the first usable applications we wanted to build. Each was hooked, seeded, decomposed into intents, kept as genes, expressed in sessions — around the graph again and again, until the bundle came out the other side. Use them as they are, reshape them, or build something completely different on the same substrate.

The hard problems are solved once, in the core, by a curated set of primitives combined into a coherent whole: peer-to-peer networking built on iroh, collaborative documents on Loro (a CRDT in the Automerge family), synchronization on Willow, decentralized authority, portable UI. On top of it you are free to make any software you want: modify what you’re running, in place, while it runs, and hand the modification to a friend.

It is early and rough — that is the point. Join the waitlist above and the bundle reaches you as soon as it’s ready — yours to use, and to shape.

The complete 0ntology of creation

Every computer sorts your world into categories. Almost always they are hidden, and chosen by someone else. This one shows you its categories — the complete ontology — and on your own machine you can change them, down to a single record. The canvas below holds the thinking that went into the first applications we built on the runtime: the seeds they grew from, the design decisions behind chat, files, and agents, the affordances they define, and the bundle that came out the other side. The malleable runtime’s own renderer draws it — the Rust entity-graph engine every panel is built on, compiled to WebAssembly; nothing else is fetched. Run it live: drag to pan, pinch or scroll to zoom into a class, and tap a design decision to read the document itself. What you see is a recording — on a browser with WebGPU, the graph runs live.

Recorded frame of the ontology entity graph: class nodes on warm paper, connected by engraved edges

x0k-ui-render-vello · entity graph · wasm32 · recording