I've kept production runningfor nearly thirty years.I hold agentsto the same standard.
Servers first, then estates of them worldwide, then the cloud platforms behind regulated financial products. The agents I run now get the same treatment: an owner, a permission boundary, a reviewer before anything merges, and a human at every decision that costs money or goes public. That's the discipline I want to bring to a team that's trying to get agents past the demo.
Where I fit.
The useful version of any title is the problem I get handed.If you've got something complex that needs untangling, a migration that has stalled, or a platform nobody quite understands any more, that's the work I'm best at and the work I enjoy most. The newest version of that problem is an agent that's allowed to do real work, and a team that has to be able to trust it.
The infrastructure half.
I've been the engineer, the architect, the consultant and the manager on platforms people depend on, from server rooms to the public cloud foundation that let seven data centres close. That's why I can sit with the team doing the work and the leader who has to sign off on it.
The AI half.
At my last company I was one of the early, heavy users of AI-assisted engineering, and I built the system that ran my team's board, documentation and weekly reporting. On my own time I run a multi-agent operation under the same rules I'd hold a production team to. The record is below.
What I build.
Four things every role in my operation gets before its first run.Each role gets a written remit, the tools it needs and nothing else, and a hard stop at money, secrets, production changes and anything public. That's set before the first run.
A role doesn't merge its own code. A fresh reviewer reads the change, posts a verdict, and only an approve moves it. It's the rule I'd hold a human team to, and it catches the same things.
Every role keeps a checkpoint of where it is, refreshed at each hand-off and enforced by a hook that refuses to let a session end stale. Work continues across restarts without anyone re-explaining it.
Scheduled wakes, overnight shifts, a wake chain that re-arms itself, and a message to me the moment a decision is mine: spend, anything irreversible, anything with my name on it.
The record.
My own operation, counted from its pull request history on 2026-09-13. The repositories are private, so the counts are mine to stand behind.One night, from the pull request history: roles, gates, and the line that waits for me.
What this isn't
It isn't a product I can demo, and it doesn't run inside anyone else's company yet. It's the discipline, proven on my own work since April. The code and the organisations are private. The employer system that ran my team's reporting stayed with the employer.
How I work.
CliftonStrengths put names to five things I'd been doing for most of my career. They're in the order they came out.01Responsibility
If I own it, I've thought it through, and you'll hear about a problem the day it happens.
“You take psychological ownership of your commitments. You are dependable and embrace values such as honesty and loyalty.”
Gallup’s definition of Responsibility
The part of my report I recognize most isn't the dependability, it's the thoroughness that sits in front of it. I explore a lot of angles before I act, which is probably why people hand me the plan, the schedule and the thing that has to land.
The other half is less comfortable. I genuinely regret producing a poor result, and that feeling does a lot of the driving. I learn from my first mistake, not my third one, and I'd rather tell you the day it happens than manage it quietly.
02Ideation
I usually have an option that didn't come from inside the room.
“You are fascinated by ideas. You see connections that others don't and can view the world from different perspectives.”
Gallup’s definition of Ideation
I've worked in enough places to have seen most problems solved a different way, so I draw links between facts, people and solutions that don't look related at first. What that produces is options, several of them, each with what it actually costs.
I hold them loosely. You'll get my recommendation, and if the decision goes the other way I'll back it and help make it work. I only get loud about a technology when it elegantly solves a real problem.
03Relator
I learn a system by asking the people who run it.
“You enjoy close relationships. You find deep satisfaction in working hard with friends to achieve a goal.”
Gallup’s definition of Relator
The short definition is about close relationships, but my own report is closer to what I actually do: I fill my head by asking questions, listening, and picking up the background from whoever I'm working with.
What I'm after is what someone is trying to accomplish over the next few weeks or the next few years. That explains why they behave the way they do in a room, and it's usually the fastest route to the real problem. It's also where the coaching starts, because once I know something I want to hand it on.
04Maximizer
I'd rather build on what someone's good at than grind on what they're not.
“You consistently ask, ‘How can we make this better?’ You don't settle for ‘good enough,’ but push for excellence.”
Gallup’s definition of Maximizer
I know what I'm good at and I'd rather spend my effort there than patch every limitation, and I manage the same way. Notice what someone is doing well, tell them specifically instead of generally, then hand them more of the work they're best at. That compounds. Grinding on weaknesses mostly doesn't.
It's the same instinct behind caring about the last ten percent, the documentation and the operational readiness, because that's where good work either sticks or quietly falls over.
05Futuristic
I can see where something's going, and I want to start building it.
“You vividly imagine the future. You inspire and energize others with your vision of what could be.”
Gallup’s definition of Futuristic
I think in vivid pictures about where something is going, months or years out, and a lot of my career has been being the person asked to paint that picture for everyone else. The honest cost is that today can feel ordinary next to it.
Once I can see what's possible I want to start, and I'll work hard to breathe life into it. Right now that picture is AI, which is why I'm not content to read about it.
CliftonStrengths® is a registered trademark of Gallup, Inc. Assessment taken January 2024.
The arc.
The equipment got bigger and less physical. The job didn't change.The physical layer
Electronics school, then a repair counter and four years of desktop support.
Estates, not machines
1,400+ systems worldwide under one management platform, and the first team of my own.
Public cloud, for real
One of the eight who built the AWS foundation that let the company leave seven data centres.
Owning the platform
Full accountability for the cloud platforms behind regulated financial products in North America and the UK, with a team of six across time zones.
Agents in production
The discipline above, on my own systems, since April.
Let's talk.
Best fit: forward-deployed engineering, AI platform and enablement work inside regulated enterprises, and the cloud platform ownership under it. I've spent a career in the room with engineers, security teams and executives, and I ship the first thing that runs in production.
Looking for a consultant rather than a hire? That's Sovereign Technologies.