The Backstory Is Live. Tomorrow, Y'all Get the Mess as It Happens.
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.
Project Ceylon Development Journal — September 6, 2026
Well, this has been a day.
When I started this morning, most of Project Ceylon's history existed in exactly the places you would expect a long-running personal engineering project to keep its history: old notes, specifications, source trees, test results, conversations, half-remembered design decisions, and a collection of moments where I was absolutely certain I knew what I was doing right up until the math informed me otherwise.
Tonight, most of that story is finally public.
We went back to the beginning and built out the Project Ceylon Development Journal on The Weekender Report.
Not the sanitized beginning.
The actual beginning.
The question was: what if Amiga development had never stopped?
From there, the journal works its way through the research into what actually made the Amiga interesting, the Video Toaster, the old NewTek source and development documentation, Project Nu-Day, QEMU, graphics experiments, the Intel Arc A770, the move to a security-certified microkernel architecture, and eventually the realization that Nu-Day had become too small for the operating system growing inside it.
That last part is important.
I Didn't Want to Rewrite the Past
One of the things I specifically did not want to do was write this like we knew where everything was going from the beginning.
We didn't.
I didn't sit down one morning with a complete architecture diagram for Ceylon and spend the next several months dutifully implementing boxes.
There were wrong turns.
There were ideas that looked good until they were tested.
There were things that worked technically but turned out to be the wrong product direction.
And there were moments where I ran the numbers, stared at the screen for a while, and thought something along the lines of: well, hell.
The early Nu-Iris display work was one of those.
The display path could do useful things.
That wasn't the problem.
The problem was what happened when I started asking it to scale into the high-resolution video workstation I actually wanted to build.
The math didn't care how much I liked the architecture.
It wasn't going to work the way I needed it to.
I was irritated.
I remain perfectly comfortable admitting that.
Engineering blogs have a bad habit of turning every failure into some sort of inspirational corporate lesson: "We discovered an exciting opportunity to rethink our architecture."
No.
Sometimes you discover that something you spent a bunch of time on isn't going to work and you're pissed off about it.
Then you go eat enchiladas and look at it again tomorrow.
That's part of the story too.
The A770 Story Is Finally in There
We also got the Intel Arc A770 story written down properly.
I'd been concerned that people would look at the card and assume the decision was basically: 16 GB GPU. Fast. Cheap enough. Good.
That wasn't it.
The development information Intel makes publicly available was one of the reasons I was willing to take the card seriously in the first place.
If you're building your own operating system, documentation starts becoming a hardware feature.
Y'all can sell me the fastest device on Earth, but if the only programming documentation consists of a marketing brochure and some guy on a forum saying, "I think this register does something," we've got a problem.
Intel gave me something I could actually research: architecture documentation, programming material, open-source compute runtime, media-driver source, Linux driver documentation. Enough material to begin understanding what the device expects from an operating system.
That doesn't make writing an A770 driver easy.
It merely changes the problem from witchcraft to a really large engineering project.
I'll take the latter.
Nu-Day Gets Its Proper Ending
The other story I wanted to get right was why Nu-Day failed.
It didn't fail because nothing worked.
That's almost the opposite of what happened.
Enough pieces started working that it became increasingly obvious I was no longer building a media workstation.
To build the media workstation, I needed an application environment. And a filesystem. And networking. And identity. And authentication. And service lifecycle management. And hardware isolation. And management interfaces. And cryptographic services.
And eventually you have to look at that list and admit something.
You're building an operating system.
Worse yet, you're building a general operating platform while still trying to describe it as one specialized workstation.
Nu-Day worked well enough to prove I was building the wrong-sized project.
That's where Ceylon really started.
And Now We're Caught Up
That is probably the biggest thing we accomplished today.
The journal now has a beginning.
Someone discovering Ceylon for the first time doesn't have to land in the middle of some discussion about IPC contracts, SecureRandom, application slots, or GPU command submission and wonder what sort of lunatic decided this was a sensible weekend project.
They can start with the innocent question.
Then watch it gradually get out of hand.
Which is much more accurate.
We also put together a shorter review piece that pulls the major parts of the story into one article.
That's intentional.
The full journal is for somebody who wants to follow the project.
The review piece is for somebody who needs to decide whether the project is interesting enough to follow in the first place.
Those are different jobs.
Tomorrow Is Different
Up until tonight, the journal has mostly been reconstruction.
Tomorrow that changes.
The backstory is caught up.
From here forward, the journal becomes what I actually wanted it to be: a running record of the project while I'm building it.
That means some entries will probably be long.
Some will be technical.
Some days we'll close a major architecture gate.
Some days we'll spend six hours chasing something that turns out to be a hard-coded number.
Some days I'll get something running that I've been trying to make work for a week.
And I'm sure there will be days where the entire update amounts to: nothing worked today.
That's fine.
I don't want to write the polished version of this three years from now and accidentally convince myself that I knew what I was doing the whole time.
I'd rather leave the fingerprints on it.
So, as of tonight, the retrospective is done.
Tomorrow, y'all get the project in real time.
The things that work. The things that don't. The things I change my mind about. The occasionally questionable engineering decision. And whatever dinner happens to be when I finally shut the computer down.
Right now I'm thinking brisket sounds pretty good.
But that's tomorrow's problem.
Originally published on The Weekend Report: https://theweekendersproject.com/report/the-backstory-is-live-tomorrow-yall-get-the-mess-as-it-happens