When Brian Madison talks about how to work with AI assistants, he draws a line between two arrangements that sound similar but aren't. In the first, you do the work and the AI helps: you write the email, it polishes; you draft the plan, it critiques. The human is in the loop — inside it, doing the labor with a tool nearby. In the second, the AI does the work and you supervise: it executes, you watch, correct, and approve. The human is on the loop — above it, directing rather than doing. Madison's claim is that the second arrangement is where things are heading, and that it's worth deliberately building your habits toward it.

I really do believe human on the loop is is the pinnacle of what to try to get to. Moving from a human in the loop to human on the loop but still maintaining that control.

The crucial word is on, not out of. This is not the pitch where you hand the AI your goals and check back in a week. The human stays in control of direction and taste; what changes is who performs the steps. Think of the difference between cooking dinner with a helper who chops vegetables, and running a kitchen where someone else cooks while you decide the menu and taste everything before it goes out.

This idea is for anyone who uses AI assistants to get things done — writing, planning, research, analysis. The practical shift is small but real: instead of asking an assistant to improve something you made, you describe what you want, let it produce a full attempt, and spend your energy reviewing rather than creating. The appeal is that your effort goes into judgment — the part assistants are weakest at — while the tedious execution happens without you. If you've ever spent an afternoon carefully editing a draft that an assistant could have regenerated in thirty seconds, you've felt the pull of this model.

Honesty requires a caveat about who Madison is actually talking to. He builds BMAD (he calls it BMED in the quote below), a framework for orchestrating AI agents that is aimed primarily at software developers. His own framing of the idea comes from that world:

I personally build BMED around the idea of you are on control. The agent is guiding you through it using it as a partner.

So the tooling he describes is developer tooling, and the workflows he has in mind are developer workflows. That doesn't make the underlying idea developer-only — the principle of delegating execution while keeping control transfers fine to anyone's work — but it does mean the polished, ready-made version of it exists mostly for programmers. For everyone else, "human on the loop" is currently more of a working posture than a product you can install.

On that point, be clear-eyed: this is a philosophy, not a shipped feature with a spec. It is genuinely usable today — every current AI assistant already lets you delegate a task and review the output — but nothing enforces the discipline for you. The model also has an obvious failure mode that a vendor would not lead with: supervision only works if you actually do it. "On the loop" degrades quietly into "out of the loop" the moment you stop reading what the assistant produces, and it demands enough expertise to spot errors in work you didn't do yourself. Madison doesn't specify where the line between oversight and rubber-stamping sits, or how to hold it. What he offers is a direction to steer toward, and a reason: keep the control, hand over the execution.