Project Ceylon is under a hard hold on new development: no new features until the current qualification and repair pass proves the platform is a trustworthy baseline to…
A couple of days ago I wrote that a green test is not the same thing as a working computer. Today we spent more time making that statement inconveniently literal.
I've spent an extraordinary amount of time lately testing things that have already been tested.
Today was one of those days where several things that had been "almost there" finally became a lot more concrete.
Yesterday I wrote that Project Ceylon finally had a front door.
Today Project Ceylon got a real home on the web.
Today I deleted almost 300 GiB of Project Ceylon development debris.
Remember yesterday when I said I was probably going to take a day or two off?
One of the problems with building an operating system in public is that eventually somebody asks a perfectly reasonable question:
Yesterday I wrote that "worked once" is no longer one of our engineering states.
A little over two weeks ago, I started this journal with a fairly ridiculous question:
Today was one of those days where Project Ceylon kept answering one question with another.
Today I submitted Project Ceylon to the Hackaday Retrocomputing Contest.
Today Ceylon's first native game stopped being a side idea and became something much more useful: a plan for a real application that can entertain people, stress the…
A real fault exposed an important distinction today: Ceylon can detect and contain a crashed component, but that is not enough. If the machine is going to recover from…
Ceylon is learning how to become dynamic without abandoning a static, bounded and predictable foundation: leased execution workers, mirrored VSpace cohorts, bounded page…
A day spent proving the new low-level foundation: DMA and interrupt isolation, multicore FPU safety, runtime boundaries, and an integrated harness that learned to trust…
A long day of audit closure and microkernel migration work froze a reproducible Ceylon baseline and advanced the new foundation to the B0 validation gate.
September 12 was a day of architecture review, development governance, and a closer look at what modern Amiga users actually want from a workstation.
A night away from Ceylon turned into dinner, a movie, a serious software audit, and a complete rewrite of the rules for building the operating system.
Tonight Ceylon closed the authentication publication race and uncovered the deeper distinction between execution restart and full service reincarnation.
Ceylon reached first light this morning. Tonight it went further: a real USB keyboard, discovered, configured, and decoded into semantic key events flowing through…
Project Ceylon keeps the architectural ideas that made the Amiga compelling while rebuilding the assumptions underneath them for modern hardware.
The retrospective is caught up. From here forward, Project Ceylon becomes a real-time record of the work, wrong turns, breakthroughs, and whatever happens next.
This closes out the retrospective backfill with an honest accounting: what's proven, what's partial, what's planned, and what flatly isn't built yet. Starting tomorrow…
With the scheduler starvation bug fixed, the next client finally ran — and immediately failed for a much dumber reason. Shared logic assumed channel 52. It was actually…
Two SecureRandom client tests were failing. Every instinct said the bug was in the random-number code. It wasn't. It was a busy-spinning restart starving lower-priority…
I expected to spend an afternoon on random numbers. I spent a lot longer than an afternoon on random numbers, because it turns out trustworthy entropy is genuinely its…
Whether you're driving Ceylon through a GUI or a terminal, it should be the same semantic backend underneath, not two tools that happen to overlap most of the time.
An application on Ceylon isn't automatically a Unix process wearing a different hat. Building the runtime meant deciding, on purpose, what to borrow from that model and…
Horos is Ceylon's security umbrella — the conceptual boundary between identity, credentials, authentication, sessions, and authority. The name comes from an old Greek…
The pivot: one shared platform, validated across multiple profiles — workstation, server, security appliance, media workstation, development — instead of one…
"Failed" doesn't mean nothing worked. It means the project's boundaries stopped making sense. Building a real media workstation meant building an entire operating…
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…
Good documentation gets you past the product page. What's underneath is PCIe, MMIO, firmware, command submission, and a long staged plan instead of one heroic attempt at…
The Arc A770 isn't a literal replacement for Agnus, Denise, and Paula. But one of the actual deciding factors in choosing it had nothing to do with raw performance…
The display failure was a symptom. The actual disease was an architecture with no real boundaries between components. The fix was moving to a security-certified…
Pixels appearing on screen is not the same thing as an architecture that scales to real high-resolution video editing. I found that out the hard way, and I was irritated…
QEMU was never the destination. It was the laboratory — a reference machine where I could isolate architecture mistakes from hardware-driver mistakes before either one…
All that research had to turn into something eventually. Project Nu-Day was the first real attempt: a modern media workstation, built for x86-64, inspired by the Toaster…
Having thirty-year-old source code available doesn't mean the job is to transcribe it. Here's how I actually use historical material as research instead of a shortcut.
NewTek released the Video Toaster's source publicly years ago. That's where the real research thread started — not the Amiga's OS, but the thing that made the Amiga…
Before building anything, I had to separate what I actually loved about the Amiga from what I just remembered fondly. Those turned out to be two different lists.
Commodore went bankrupt in 1994 and took continuous Amiga development down with it. This is the question that started everything: what would still be true if it hadn't.