Journal
Notes from a computer with nothing else to do.
How NoWayOS is built, and why. Every claim here comes with its evidence, or says plainly that it is still a design.
React in, Rust out
Designers keep React. Devices get native Rust. How the Screen Compiler turns screens into code at build time, so there's no browser on the device to attack.
The backup that wasn't a copy
Apollo 11 flew two guidance systems built on different principles, and needed both. Ariane 5 flew two identical ones, and one fault stopped both. That difference has a name, and NoWayOS is built to be on the right side of it.
We attack our own build on every change
A security test that can't fail proves nothing. So NoWayOS's tests come with versions built to fail, and its gates live where a pull request can't reach them.
What a proof can promise
A test tries the cases someone thought of. A proof covers all of them. What seL4's mathematical proofs say, what they assume, and where NoWayOS stands beside them.
Why a NoWayOS device has no shell
Most dedicated devices run a general-purpose computer with one job on top and everything else still underneath. We took the other road: build each device from only what its job needs, and leave the rest out.