Not ready to install
Follow the build.
Every step is written down as it happens: what was tried, on which machine, and what failed as well as what passed. The longer write-ups are in the Newsroom.
From here to a release.
Step 1, under way
Proofs
Small experiments for the riskiest ideas: the undo timeline, why, surviving a graphics reset, text rendering, and sleep. A proof that fails changes the design.
Step 2, begun
Preview
An image that starts on both machines, with the base, the desktop and five apps: Files, Browser, Settings, Terminal and Store. For invited testers. It may break, and it says so. Its base image runs so far in a virtual machine.
Step 3, not started
First release
A laptop system that one person can live on, small and finished. It proves the two promises on two machines.
There are no dates here. Nothing has been built or measured that would make a date honest.
What has happened so far.
Newest first. Each result names the machine it came from.
- 16 November 2026
- The Dell starts from an image built from the project's own recipe, with the drawn sign-in screen and real blur behind windows and the sign-in fields.
- 16 November 2026
- Rupa's four materials are named and drawn: Ice (Stone in the dark), Fog, Mist and Shade.
- 14 November 2026
- The Preview's base image: signed updates, rolling back after a failed health check, and the config file with its undo timeline all worked, in a virtual machine on the Dell. Nothing of it runs on a laptop yet.
- 14 November 2026
- why, first version: written in Rust and built on the Dell. It answers four questions, and passed 15 of 15 checks against real records, five times over.
- 14 November 2026
- Proof 5, sleep, on the Dell: it slept and woke 88 times of 88. It reached the deepest sleep only with one kernel setting, because the firmware reports a power-saving feature as unsupported. The overnight round is still to run.
- 14 November 2026
- Proof 3, the graphics reset, on the Dell: the screen came back after a reset of the whole graphics chip. One app's hung shader froze the screen and pointer for 7.5 seconds, which is a failure the design now has to answer.
- 13 November 2026
- Proof 4, text rendering, on the Mac and in a virtual machine: yes, with conditions.
- 12 November 2026
- Proof 2, why, round one, in a virtual machine: yes, with conditions. Round two, on a real machine, covers the fan, battery, heat and sleep, and has not started.
- 12 November 2026
- Proof 1, the undo timeline, in a virtual machine on the Mac: every kind of change was recorded and undone with later work kept, with conditions. An update that changes an app's data could be undone once each app's data had its own snapshot.
What done will mean.
Lived on
People outside the project use it as their only computer, and none needs the terminal to repair it. The proposal is ten people for 30 days.
Both promises hold
Every system change is in the timeline and can be reversed. why answers every question on its published list.
Drawn first, then checked
Every screen was drawn before it was built, and passes the interface guidelines.
Audited
The accessibility audit is passed. An outside security audit is done and its findings are fixed.
Updated and rolled back
An update, a failed update and a rollback have each been run on both machines.
Honest
A list of what works and what does not is published for each machine.
How to follow it.
This page is the record. It changes when something is tried, and says so whether it passed or failed.
A feed, the public source or an email note: the owner's choice