About

From the service floor to the agent layer.

I'm Roody Bonnaig. I spent more than thirty years making sure people felt taken care of, in restaurants, in retail, and at a front desk before I moved into IT. Now I build the systems that do that. This is how the line connects.

Thirty-plus years with customers

The majority of my work career has been in customer service. More than two decades of it was on the floor as a server in food and beverage, with retail customer service before that. Most recently I moved into hospitality at The Boca Raton Resort: a year and a half at the front desk, then about nine months as one of the concierge supervisors, leading a team of around twelve.

You learn some things about people doing this for thirty-plus years. It taught me that people don't like to wait for what they want, and that they don't always know what they want either, so you learn to read between the lines and anticipate, and to bring a person the thing they actually came for. Quickly, because they still don't like to wait.

It also taught me the half of engineering nobody puts in a tutorial: how to sit with someone who doesn't care how the software works, only that their problem goes away. And how you earn the kind of trust where a person just hands you the keys. I've been doing that for three decades. It's the part I'm best at.

The pivot

I got tired of being the power user and wanted to build the software I'd spent years working on top of. So I moved into IT at the resort as a Support Analyst, started an Applied AI degree at Miami Dade College, and began teaching myself to ship. I'll be straight with you: I came to this later than the twenty-two-year-olds, and through a side door. What I have, however, is three decades of doing the part of the job that can't be taught quickly, and a year of doing the part that can.

The IT desk is also where I started doing the newer thing: translating between people who don't code and the systems they depend on. That part is recent. The customer half isn't.

Building with agents

Everything I've built so far, I built alongside an AI agent. I used to think that was something to hide. Now I think it's the whole point. I run a multi-agent system on Claude today, about seventeen agents working together, and I'm deliberately building it to be model-agnostic. The memory and the orchestration live in my own layer, not the vendor's: version-controlled files, a vector database I run for retrieval, and a model gateway I can repoint. Swap Claude for another model tomorrow and the system, and everything it remembers, is still mine.

That memory layer is the reason this is becoming an agentic operating system of my own, and not just a project that runs on someone else's platform. When it breaks, and it does, I'm the one who finds out why and fixes it so it doesn't break the same way twice. That's the part of the work I love most, the part where you go down to the bottom of a thing and come back up with the reason.

Web and creative work

It isn't all agents. I build and ship front-ends too: this site, a personal one, a site for my father, and the landing page for SupplyScout. I do music and video production on the side. I like making things people actually see and use.

What I believe

Memory is the system. The model is a tenant.
Most people build on a model and let it own everything: the memory, the state, the identity. I flipped it. The system of record is mine: version-controlled file contracts and a vector database I run myself for retrieval, reached through a gateway I can repoint. The model moves in like a tenant, does its work, and could be swapped for a better one tomorrow without the system losing a single thing it remembers. The intelligence is rented. The memory is owned.
Own your layer. Rent the intelligence.
A frontier model is the best thing you can rent and the worst thing to depend on. Vendors shift, prices move, models get deprecated under you. So I keep the durable parts in a layer I control: the orchestration, the memory, and the rules that govern how the agents behave. The model is a powerful, replaceable component plugged into that layer, not the foundation of it. Own the part that has to outlive any one model; rent the part that's improving too fast to marry.
A rule you can’t enforce is only a wish.
In a multi-agent system, a rule written into a prompt is a hope, not a guarantee. Under pressure the model drifts right past it. So the rules that actually matter in the Colony aren't just written down; they're enforced mechanically, by gates that sit outside the model and check the work before it lands. A destructive command, an unverified claim, a skipped safety step: each has a guard that catches it whether the agent remembered the rule or not. The principle is the wish; the gate is what makes it real. How the gates work is the part I'll walk you through in person.
Show the work before it’s perfect.
Polished demos hide how a thing actually behaves. I'd rather show the real build mid-flight: the failures, the safety gates catching mistakes, the parts still rough. That's where you can tell whether someone can really engineer. This whole site is built that way: a product, in the open, while it's still moving.
The customer doesn’t care how it works, only that it does.
Thirty-plus years on the service floor taught me this before I wrote a line of code. The person in front of you doesn't want the architecture; they want their problem gone. The engineering only counts when it disappears into something that just works for the human depending on it.
Build it so it keeps running after you leave.
The real test of a system isn't the demo. It's whether it survives without you babysitting it. Self-healing loops, backups that verify themselves, agents that capture what broke and fix it so it doesn't break the same way twice. I build for the two-in-the-morning failure I won't be awake for.

Where I'm pointed

I build the way a forward-deployed engineer builds: solo and end to end, in production. So far I've been my own first customer. I haven't been hired to do it for someone else yet, and that's exactly the role I want: embedded with a customer, turning what they actually need into something that ships and keeps running after I leave. I'm based in Coral Springs, Florida, on the Anthropic Claude certification track, and open to the right role.

See the work → · Get in touch →