Behind the name: why Ultimate Zion

I've been a technologist for as long as I can remember. It started with the early home computers, the VIC-20, the Commodore 64 and the Amstrad, and a fascination with what those machines could do. Sci-fi, robotics and AI were never far behind: WarGames, Short Circuit, Hackers, The Matrix.

Then Jurassic Park in 1993, the first time I saw CGI that looked real. My mother said she'd never seen me so mesmerised. It was the first time I couldn't tell what a machine had made from what was real. Today that's true of text, code and decisions.

So when it came to naming this site, there was only ever one option. UltimateZion has been my gaming tag for years, and it came from the films that got me here.

The last human city

In The Matrix, Zion is the last human city. Buried deep underground and running on its own terms, it's the final stronghold for people fighting to keep their freedom, identity and agency in a world run by machines.

In 1999 that was science fiction. Watching AI agents move into how we think, work and make decisions today, it feels a lot less like fiction. Most of that is useful. Some of it is happening faster than anyone is governing it.

I think we need a stronghold in the digital age: a place to understand the technology properly, question it honestly, and make sure people stay in control of the machine, not the other way round.

This site is my Zion.

Zion runs on machines

This isn't a site about fearing AI. I build AI platforms for a living: MCP services, agent runtimes, and the governance and observability around them. AI is changing how software gets built, and I'd rather help shape that than watch it happen.

The films make the point well. In The Matrix Reloaded, one of Zion's council elders takes Neo down to the engineering levels, where machines keep the city alive: air, water, power. Zion isn't free of machines. It depends on them. The question the scene asks isn't whether to use machines, but who is actually in control.

The illusion of control

The films go one step further, and it's the part that stays with me.

At the end of Reloaded, Neo meets the Architect and learns that Zion has been destroyed and rebuilt six times before. The last free city was never outside the system. It was part of it. The people of Zion believed they were in control, and they couldn't see the machinery that was actually governing them.

That's the risk I see with AI adoption. It isn't the machines themselves. It's control we believe we have and don't.

It shows up in ordinary ways. An agent calling production tools under a shared service account nobody reviews. Token spend that lands on a bill before anyone can say which team or workflow drove it. A model making decisions inside a process where no one can explain, afterwards, why it did what it did.

None of that feels like losing control while it's happening. It feels like moving fast. That's the point.

So when I talk about keeping humans in control, I don't mean a gut feeling. I mean being able to prove it: every model call, tool call and decision observable, attributable and owned by someone.

Why "Ultimate"

Six versions of Zion fell for the same reason: the people inside them didn't control the system they depended on.

When I picked the tag, "Ultimate" was simply the one that wouldn't need rebuilding. Years later, building AI platforms for a living, I read it differently. Nothing in engineering is built once and never touched again. The Ultimate Zion isn't the city that never gets knocked down. It's the one that breaks the cycle: built with its eyes open, able to see the machinery it runs on, and able to recover on its own terms.

That's the standard I want this site to hold to.

What that means in practice

• Guardrails, not gates. Governed AI adoption that lets teams move fast inside clear boundaries, instead of blanket bans or free-for-alls.
• Humans accountable for outcomes. Agents can act. People own what those actions do.
• Visibility. You can't control what you can't see.
• Economics. AI that doesn't meet its ROI isn't innovation. It's a cost centre with good marketing.
• Resilience. If the business depends on an AI system, it needs to be as available and recoverable as any other critical system.

What you'll find here

Field notes on building the platforms that make that possible: platform and solutions architecture, regionless resilience, security and governance, FinOps and token economics, and AI platform strategy.

Understand the tech. Question the algorithms. Keep humans in control.

Welcome to Zion.