The map

Start with a letter, or go straight to the technical account. These pages explain what I've been building and how the pieces fit together.

You don't need to read all of them. The letters explain why; the deployment pages describe who might use it; the odometer records how far the work has got.

"Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them." — Frank Herbert, Dune, 1965. Herbert's remedy was to ban the machines. Ours is to own them.

For my technical friends

• The disempowerment hedgeFor people who think about AGI professionally. I say up front where I'd be wrong, then ask you to break the mechanism. Start here if gradual disempowerment is already your worry.
• The north starThe technical vision: the Sovereignty Ratio, the Ownership Loop, the Exchange Dial, the unplug test, and where this sits in the landscape. Canonical for every claim on every page.

For my less technical friends

• A letter about what I'm buildingFor friends. Why I've turned down good jobs to build this, in plain terms, with the test that keeps it honest.
• The north star, in plain wordsThe whole vision for people who don't work in AI. The design, the test, and the current limits.

Thoughts on commercialization

• Where AI you own runsFor buyers. The same software at three scales: your machine, a business's hardware, an organization's racks.
• Running agents without inheriting everyone's supply chainFor security teams. The agent-era supply-chain surface, the controls that address it, and why this stack is Go bound directly to Apple's APIs.

Where I'm at

• The odometerDated status of every component (running, measured, in build, planned) and the three falsifiable lines the company won't cross.

Thinking ahead

• The Intelligence CommonsSpeculationA speculative proposal for open federated distillation, with the unresolved problems spelled out.
• An Operator's ManifestoRhetoricAfter Hughes's A Cypherpunk's Manifesto. An argument for ownership, with a postscript separating it from measured results.

Every page makes the same two promises. Results get published, good or bad. And the test never changes: unplug, and measure what still runs.