Project Nu-Day: What Actually Worked
Before I get into why Nu-Day didn't survive, it deserves an honest accounting of what it actually proved. A working path is not the same thing as a finished subsystem, but it's not nothing either.
Before the next entry, where I get into why Project Nu-Day ultimately didn't survive in its original form, I want to give it a fair accounting of what it actually did prove. It would be easy to skip straight to the postmortem and let the failure overshadow real work that got done. That's not honest, and it's not the kind of history I want this journal to be.
What had real, working evidence behind it
Inside the QEMU virtual reference machine, there was real, demonstrated evidence for boot, for storage, for logging, for clock handling, for basic display output, and for service lifecycle behavior — services starting, checking in, and in the cases where I'd actually built it correctly, shutting down cleanly instead of just vanishing. That's not a small list. That's most of what a computer needs to be recognizably a computer, working, reproducibly, in the reference environment I'd built specifically so I could trust what I was seeing.
What had real but partial work behind it
Framebuffer and presentation primitives had real work behind them, even after the Iris architecture reset — the reset changed the approach, it didn't erase everything that had been learned getting there. Early semantic work on what eventually became Nu-Iris. Input handling. Real boundaries around filesystem responsibilities. Early concepts for bulk data descriptors. Genuine IPv4, ARP, ICMP, and UDP networking work. NuBasic work on both a host development target and an early static target.
None of that was finished. All of it was real — not mockups, not aspirational diagrams, actual working code exercised against the reference machine.
The distinction that matters
A working path is not the same as a finished subsystem.
I want to sit on that sentence for a second because it's going to matter a lot in the next entry. Having a working path through a problem — this boots, this responds, this proves the concept — is real and valuable. It is not the same claim as "this subsystem is done and production-ready." Conflating those two things is exactly how projects quietly grow scope nobody signed up for, which, as it turns out, is precisely what happened here.
So: credit where it's due. Nu-Day proved a lot. The reference-machine strategy from a few entries back paid off exactly the way I'd hoped — I could trust what I was seeing, because the virtual hardware underneath wasn't lying to me. What it also did, gradually and without me noticing for longer than I'd like to admit, was reveal the actual size of the thing I'd agreed to build. That's next.
Originally published on The Weekend Report: https://theweekendersproject.com/report/project-nu-day-what-actually-worked