I Became the Loop Before the Loop Existed

By Michael Weisfeld, founder of 9xNine

I had a rough week. I think it's worth telling you about, because the thing that went wrong is the thing I'm building a company to fix.

Here's what happened. I spent the weekend prepping. I did a ton of design, made a ton of decisions, and got everything queued up. I even thought I was being clever. I scheduled a major build to kick off at 3:05 AM Tuesday, right when my tokens refreshed, so it could run unattended and get a mountain of work done while I slept. I checked in now and then. Everything looked fine. Then, after what felt like almost 24 hours of building, I actually looked. Nowhere near as much was done as I thought. I'd approved the designs. I thought it was queued. It just wasn't getting done.

That's a special kind of deflating. You do everything right and the payoff isn't there.

It wasn't a me problem

But when I stopped being frustrated and got curious, I realized this wasn't a me problem. It was an orchestration problem. I'd loaded big bundles of work and trusted them, with no acknowledgment that each piece landed and no way to see how full the queue was. So some of it fell on the floor, and nothing told me. I thought the tank was full. I couldn't see into the tank.

Here's the part that reframed the whole week for me: the discipline I need from myself right now is exactly the discipline I'm building into the system.

A cup at a time

So I gave myself a protocol. Break work into the smallest pieces that can finish on their own, nothing that needs me to step in halfway through. Make every piece leave a receipt: a note that says "received" and another that says "done." Let the next step read those notes before it moves, so nothing goes forward on an unconfirmed step. And because I can't see how deep my queue is, I stopped trying to manage it by watching. I manage it by constraining. I load 3 to 5 pieces, stop, and don't load more until I've seen the first set finish. A cup at a time. I'm not measuring the tank anymore. I only pour in what I can confirm emptied.

If that sounds familiar, it should. That's a reliability layer: receipts, small units, a cap on what's in flight. I'm hand-simulating, with a human in the loop, the exact system I'm building to run without one.

Notes that agents leave for each other

There's an idea behind this I got a little obsessed with: agents leaving notes that other agents pick up and act on. You may have seen the darker version in the news, where it gets used for mischief. The mechanism itself is neutral. It's how ants coordinate. One leaves a trail, the next one reads it and keeps going. I'm pointing that same idea at something boring and useful: getting marketing work delivered reliably. The receipts are the trail. The small units keep a whole bundle from vanishing at once. And once the receipts exist, the dashboard that tells me whether it's actually working builds itself, because it just counts the notes.

Run the manual version first

That's the lesson I'd give anyone building with these tools. You don't wait until the autonomous system is finished to start getting leverage from it. You run the manual version of the same discipline, and you close the gap as the system catches up.

This week I didn't get my 6-hour walk-away. I got my 1-hour ones back.

That's not nothing. That's me becoming the loop, until the loop can be me.