Seven questions decide whether your AI agent ships. Most teams can answer two.

A new class of company has taken up position around the agent economy, and they are the ones who decide whether your agent gets to ship. They do not build models. They are not on most teams’ AI stack roadmap. But every serious production agent has to pass through them, and most agent proposals on a CIO’s desk right now have no answer for what those companies are about to ask.

The model is one piece of the agent economy. The control layer is the other.

The control layer is the set of infrastructure decisions that determine whether a model’s output is allowed to act in the world. Where does the agent live. What state does it remember. Who is it acting for. When does it need approval. What can it spend. Who can stop it. None of those questions get answered by a model. They get answered by the companies sitting between the model and your production system, and the last six weeks have made it obvious who they are. Cloudflare ran Agents Week. Stripe expanded its Agentic Commerce Suite. Okta launched Okta for AI Agents and expanded it again this month. Auth0 has been publishing AI Agents docs. Datadog has been turning LLM observability into something that looks a lot more like an agent control plane than a logging product.

I’ve covered the protocol stack already — the six protocols that emerged and the three that decide which agents survive. This piece is about the operators sitting above the protocols. The companies turning agentic behavior into controlled, permissioned, auditable infrastructure. The companies your security review is about to discover the hard way.

Here’s what’s inside:

• The seven-row control map I would put in front of any agent proposal before it touches a production system, and the one question per row that flushes out the gap.

• Why Cloudflare, Auth0, Snowflake, Stripe, and Datadog are becoming the operating system of the agent economy, and what each one is actually trying to own.

• The kill switch most teams do not actually have, even though they think they do — and the five layers it has to be implemented at to be real.

• A real data leader’s failure mode, live this quarter: her agents are routing around the human permission structure, and she now owns three questions she did not yet know how to answer.

• The three prompts paid subscribers get this week. A control-map fill-in for the agent your team is most likely to ship this quarter, a pressure-test for the next vendor pitch on your desk, and a five-layer kill-switch audit for the agent that actually scared you.

The boring layer is where the power is moving. Let me walk you through the map.