Signed boot
Every boot image in the current boot chain is verified as signed. Secure Boot has been on and enforcing on Anthony's laptop since 26 September 2026.
An introduction · status as of 27 September 2026
A daily desktop, a server in alpha, and a home edition in test. The daily desktop is built on NixOS and GNOME. Anthony Collado develops d0 OS independently; it is not yet a public software release.
01 / the desktop · in daily use
GNOME underneath, the d0 look on top. Secure Boot is on and enforcing with d0's own signing keys. Updates can apply without a reboot when the kernel is unchanged; a kernel update still needs a supervised reboot.
Every boot image in the current boot chain is verified as signed. Secure Boot has been on and enforcing on Anthony's laptop since 26 September 2026.
Hourly local snapshots let Anthony restore an earlier version of a file. They are on the same disk and are not a backup.
This daily-use build has been tested on one laptop. It is not evidence of support for other hardware.
02 / remote desktop · in daily use
Sit at another computer from yours. Saved computers and computers on your network appear in one list. You can connect with one click; each computer's identity is checked and remembered.
The connection uses TLS and pins the computer's certificate. If the identity changes, the client shows the change and does not connect unless d0 OS Server vouches for it. Sign-in with a d0 account is live on the alpha server; a one-connection password is fetched for the session and is not written to disk.
03 / agent workspace · in daily use
A desktop workspace to reopen AI coding sessions, organise agents into groups, and handle tasks and decisions in one place. The core Console runs in daily internal use.
An optional GitHub connection is working in test. It is not a customer release; its end-to-end tests used a local test repository and a simulated API. No real GitHub account was connected.
The memory layer: d0fs04 / d0 OS Server · alpha
d0 OS Server manages accounts, computers and their software inventory, certificates and health checks from one test server, using the D0 Server Manager web console. The broader product is still in development.
One account per person for the server desktop, Remote Desktop and the admin console, with groups, per-user licences and an audit trail, run from the D0 Server Manager web console.
Enrolled computers report inventory, software bills of materials, compliance and bounded hardware summaries.
The test server checks its own health every minute. Alerts can wait, fire and clear; monitoring is still in test.
A private certificate authority is also in test on the server. Devices must trust its root; it does not issue publicly trusted web certificates. Nothing on this page claims a production service or customer deployment.
05 / d0 OS Home · in test
d0 OS Home is being built with guided setup, everyday apps, family tools, backup and updates. In a 27 September 2026 virtual-machine test, its installer booted under UEFI, installed offline and started Initial Setup from the installed disk. A person then created an administrator account through the actual setup pages.
Evaluations of the Home, Pro and Enterprise tiers passed, and so did a one-shot update boot test of Home. The edition is not available for download and has not been tested on consumer hardware.
06 / working with other systems · in test and planned
Windows file handling and the App Installer are in test. They are not a public release or a claim of full compatibility.
29 Windows file extensions, across 23 file types, open in d0 OS (checked 27 September 2026): shortcuts, remote-desktop files, saved mail messages, Windows help files, and virtual disks, which open read-only. Script files are shown rather than run by accident.
In a real-download test on 26 September 2026, PuTTY, 7-Zip File Manager, Notepad++, VS Code, Claude and the ChatGPT sign-in screen opened as windows. A Mac download inspector can read app metadata; it does not run Mac apps.
An app for Windows PCs is a design. It has not been built or released.
07 / the memory layer · local tools in daily use
Local d0fs tools and agent hooks run daily on the development machine. They keep versioned work records and bring relevant context into Claude Code and Codex sessions. The shared d0fs service is in test, not cut over.
The memory layer: d0fsFollow the work
It is not for sale or download yet. Write to Anthony about your use case, an early test, or a research question.
I · d0 OS
Next chapter
Versioned work memory for AI agents.