By Ryan Low, CBAP — independent business analyst, Digital Block FX

Your company is probably running a dozen AI assistants right now. Ask who approved what any of them did last Tuesday. In most companies, nobody can answer.

That gap has a name this year. People are calling it AI control, and it has quietly become a bigger argument than which model is best.

Two very different machines

Jarvis answers to one person. He lives in Tony Stark’s head, he is brilliant, and nothing he does is written down where a second person could read it. Take Tony out of the room and the system goes with him.

That is what most business AI looks like today. Clever helpers, one per person, each with its own instructions, its own settings, its own quiet reach into company data. They work. They just don’t answer to the company.

The Enterprise computer is the opposite, and it is boring on purpose. It answers any of the crew, at the level of authority that person holds. It says what it is doing. It keeps a record. And when the order is big enough, it stops and asks the captain first.

Nobody falls in love with the ship’s computer. That is rather the point.

I’ve drawn that line before, in Two Kinds of AI at Work. What has changed since is that the market stopped treating it as a metaphor and started shipping it as a product category.

The market just gave it a name

You will hear “control plane” and “harness” a lot this year. Both describe one layer sitting between your people, your data and the models, deciding what is allowed to happen.

Every major vendor is shipping one now. So let’s concede the obvious: having a control layer is no longer a difference. Everyone has one.

What is not settled is whether yours holds up when something goes wrong. Gartner put a figure on that in May. By 2027 they expect 40% of large companies to demote or shut down their self-running AI agents over governance gaps — gaps found only after a live incident. Not because the models were weak. Because nobody could prove what happened.

Rank, not a switch

Gartner’s advice is that one rule for every agent is the mistake. I would agree, and put it more plainly. A ship’s computer has ranks. Your AI should too.

Watching. It reads and reports. It changes nothing.

Advising. It drafts. A person decides.

Asking. It can act, once someone with the authority says yes.

Acting. It runs on its own — and this is the one that needs a brake.

Rotational Labs built a vendor-questionnaire review system on exactly that line. Two models score each questionnaire, and the client’s own analysts review only the cases where the two disagree. Rotational’s published figures put it at roughly 20,000 analyst hours a year taken out of the job, with the scoring coming out about 27% more accurate. The control was not a limit on the work. It was the reason the work could be trusted at that volume. Their case study is here.

Where the enterprise line falls

Three questions tell you which kind of system you have.

Can you show, months later, which agent did what, and on whose authority? Does your private data stop at a boundary you chose, before it ever reaches a model? And if the vendor vanished tomorrow, do you still own the work?

A consumer tool answers those with a screen. An enterprise system answers with a record.

The control layer I implement on is Endeavor, from Rotational Labs — prototyping, evaluation and runtime for agents, running in their cloud or inside your own environment, with every step, every record and every dollar visible as it happens. I am an independent business analyst and implementation partner, not a Rotational employee; I recommend it because it is what I would want running my own operation.

If you cannot say who approved your AI’s last decision, that is the place to start. Describe one workflow and I will show you what a governed version of it looks like — or book a call.