Skip to content
Strategy
Jul 15, 2026 · 2 min

Approval is a feature, not a limitation

The AI can draft anything it likes. The one thing it can't do without me is touch the real world.

Governance
Trust
Human-in-the-loop

The scariest AI demos are the ones that work. Something runs off and does the whole job, and nobody can tell you what it just touched.


The demo that sells, the product nobody can trust

I've watched this pitch a hundred times. You describe a goal, the system disappears, and a minute later it reports back: site updated, emails sent, records changed, all handled. On stage it looks incredible.

Then I picture handing that to one of my clients and the whole thing falls apart. Not because it acts. Because I can't see what it knew, what it decided, what it changed, or why. When something breaks, and something always breaks, there's no thread to pull.

So I built Nuva around the opposite instinct. I'm not trying to take the human out of the loop. I want to make the loop something you can actually read.

Fast and reckless are not the same thing

Everyone tells small companies to move fast. Fine, until "fast" starts touching things you can't undo.

Publishing to a live site, spending a budget, emailing a customer, deleting a record. That is not the same class of action as writing a draft. A system that treats all of them as equally safe isn't fast. It's reckless with a nice interface.

Nuva draws a hard line there. Analysis, drafting, preparation: those run freely, because they produce a recommendation, not a consequence. The moment a recommendation turns into something the outside world can see, a person approves it. That approval isn't friction bolted onto the product. It is the product.

What I actually guarantee

Evidence before confidence. Saoul, the SEO specialist, hands back findings with the pages, signals and numbers behind them. You see why before you touch anything.
Approval before impact. PERI, the website specialist, prepares the change and a preview. It goes live only when you approve, and that approval is a recorded event, not a shrug in a chat.
A history that survives. Observation, recommendation, approval, result: the whole path outlives the conversation. Come back in three weeks and you can still reconstruct what happened.
Boundaries that hold. Everyone works inside a workspace, with a role, against the capabilities they're allowed. A specialist can't reach past that.
You get the last word. When you overrule the system, you win, and that gets captured too. Override is normal, not an error.

None of this is exotic. It's what any serious business already expects from the people it hires. I just hold the AI to the same bar.

The founder is not the bottleneck

Here's the fear I get thrown at me: keep a human in the loop and you've just rebuilt the traffic jam. True, if approving meant redoing the work by hand.

It doesn't. The specialists gather the evidence, write the brief, prepare the change. You make the one call only someone with the full picture should make. Approve these priorities. Publish this. Hold that one.

Taking the founder out as an integration layer and taking the founder out as a decision-maker are opposite goals. Nuva does the first and protects the second.

Autonomy you can't inspect isn't something anyone responsible can buy. Control isn't the tax on the value. It is the value.


If this is the thread you care about, I've pulled on it before:

Want to discuss multi-agent patterns?

We love talking about orchestration, AI workflows, and engineering challenges.