Why a Modern Amiga Needed a Secure Multicore Microkernel
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 microkernel foundation.
The display math failing wasn't really a display problem. It was a symptom of something bigger: the early architecture didn't have real boundaries between its pieces. When one part misbehaved, or scaled wrong, or made a bad assumption, there was nothing structurally stopping that from becoming everyone else's problem too. That's fine for a demo. It is not fine for anything I'd want to call a real platform.
What 1985 could get away with that 2026 can't
The Amiga's security model — to the extent "model" is even the right word for it — assumed one person at the keyboard, running software that person chose to run, on a machine that was never going to sit exposed on a network being poked at by things nobody invited. That was a completely reasonable assumption in 1985. It is not a reasonable assumption for a long-lived, networked, modern machine in 2026, one that's going to run software I didn't personally audit line by line, handle data I don't fully trust, and stay running for a long time without a reboot fixing whatever's wrong with it.
A modern continuation of this machine's philosophy needed real fault isolation. Real authority boundaries — not "this program probably won't do anything bad," but structural guarantees about what a given piece of code is and isn't allowed to touch. The ability for one service to crash, misbehave, or get compromised without taking the rest of the machine down with it. And underneath all of that, multicore support done properly, because "properly" was never going to mean "one core doing everything while the others watch."
The foundation, and what I will and won't say about it
This is the point where I need to be direct about something I'm keeping deliberately vague, on purpose, permanently: I'm not going to name the specific microkernel underneath this project. Publicly, this runs on a security-certified microkernel foundation, and that's the extent of what I'll say about the specific technology choice in this journal, now or later. That's not me being coy for dramatic effect — it's a boundary I've set for how I talk about this project publicly, and I'm going to hold it consistently across every entry in this series, not just this one.
What I will talk about is the reasoning, because the reasoning is the actually interesting part anyway. A security-certified microkernel foundation gives you capability-style authority instead of ambient trust — a piece of code can only do what it's been explicitly handed the authority to do, not whatever the OS happens to allow by default. It gives you services that can restart independently instead of taking the whole machine down with them when they fail. It gives you a foundation that was actually built and verified with the assumption that hostile or buggy code is going to show up eventually, instead of a foundation that assumes good faith from everything running on it.
What this actually changes
This is the point where "a modern Amiga" stopped being a slogan and started being an actual architectural commitment. The custom-hardware-as-division-of-labor idea from the original machine doesn't go away — it gets stronger, because now each piece of specialized work can live in its own properly isolated service instead of all sharing one undifferentiated address space and hoping for the best. Fault isolation and the Amiga's original "let the right hardware do the right job" philosophy turned out to reinforce each other instead of fighting each other, which I honestly wasn't sure would be true until I was well into building it.
This decision is still standing today. It's the actual foundation everything downstream of this entry gets built on. Next up: the hardware side of the equation, and a decision that turned out to hinge less on raw horsepower than I expected, and a lot more on something Intel does that a lot of vendors don't — they actually tell you how their hardware works.
Originally published on The Weekend Report: https://theweekendersproject.com/report/why-a-modern-amiga-needed-a-secure-multicore-microkernel