Project updates, architecture notes, and milestones.
In August, I ended with this sentence:
Then I want to get Open Nexus OS running on real RISC-V hardware, with real graphics hardware and real drivers.
That sentence was easy to write.
An operating system that only boots in an emulator is a promise. It becomes a serious project the day it runs on a board you can buy.
I don't want to replace Linux.
In fact, I probably couldn't have built Open Nexus OS without Linux. I use Linux every day, and for general-purpose computing it is an extraordinary piece of software.
So whenever I say that I am building a different operating system, I expect the obvious question:
Why didn't you just modify Linux until it did what you wanted?
That question is actually what led me to build this.
In June, we ended with a promise: the screen is on — now we teach it to think.
Our own language. A shell. A launcher that feels like home.
Six weeks later, all three exist. And a few things we didn't promise, because we didn't yet know we'd need them.
In March, we showed you a kernel that could explain itself.
Today, it can show itself.
Three months ago, NEURON was an argument. A set of papers. A microkernel you could measure, but not see. There was nothing on the screen — because there was no screen.
Open Nexus OS is no longer just a set of ideas, prototypes, or isolated implementation decisions.
It is becoming something more important: an architecture that can explain itself.
That is why we published this paper set.
Not to decorate the project with academic language.
Not to turn engineering into performance.
But to make the core decisions around NEURON, our Rust-based capability microkernel, explicit, citable, and reviewable.
If you come from a university lab or a research institute, you usually don’t ask, “Does it boot?” You ask the questions that matter long-term:
This is the current answer for Open Nexus OS.
At first, an OS feels like progress.
Things compile. Services start.
You can point at features and say, “Look—momentum.”
Then the truth shows up:
Most “working” systems are simply lucky systems.
They work until contention shows up. Until timing shifts. Until a second core enters the room.
So we changed the objective.
Not “add more features.”
Not “move faster.”
Replace luck with proof.
When I first started Open Nexus, I took the pragmatic path:
build on Redox's proven microkernel, focus on the UI layer, ship faster.
It worked. We had a login screen, a launcher, a control center.
The foundation felt solid. Redox was Rust-native, microkernel-based, open source.
What could go wrong?
When we first introduced Open Nexus, it was only an idea — an alternative to fragmented ecosystems, built on Rust and a Redox microkernel.
Today, that idea has taken shape. The foundation of the project is no longer abstract; it is code, libraries, and a working environment.
Every major shift in computing began with a small group of people who believed that the status quo was not enough.
Today, that status quo is fragmentation: phones that don’t talk to desktops, ecosystems that trap you in silos, and platforms that put business models above users.
We believe this is the moment to change that.
And we’re building the system to prove it.