The Mixed Agent Enterprise

Enterprises are unlikely to build one standardized population of agents.

They will have many.

Agents built internally.

Agents embedded inside enterprise software.

Agents supplied by model providers.

Agents delivered by cloud platforms.

Specialist third party agents.

Open source agents.

Agents created by individual employees and teams.

The future enterprise may therefore contain hundreds or thousands of computational actors built by different organizations and operating under different technical assumptions.

That creates a new operating problem.

“How does an enterprise govern an AI workforce it does not fully own?”

Agent sprawl changes the control problem

Traditional enterprise systems have users, applications and services.

Agents introduce actors that can reason, choose tools, initiate actions and potentially coordinate with other agents.

Now consider what happens when a Salesforce agent interacts with an internally built agent, which calls a specialist service, which updates an enterprise system and triggers another workflow.

Who owns that chain?

Which identity acted?

Whose permissions were used?

Which system retains the memory?

Who pays for the execution?

Who evaluates the result?

Who can stop it?

The problem is no longer simply deploying agents.

It is governing relationships between agents, systems and humans.

Ownership and control are different

An enterprise may own an internally developed agent.

It does not own the agent embedded inside every software platform it purchases.

But the enterprise remains responsible for what happens inside its operating environment.

That means control cannot depend entirely on who built the agent.

Common operating mechanisms become increasingly important:

• ·Identity.
• ·Permissions.
• ·Delegation.
• ·Tool access.
• ·Observability.
• ·Evaluation.
• ·Cost attribution.
• ·Versioning.
• ·Incident response.
• ·Termination.

These capabilities need to work across a heterogeneous environment.

The control plane becomes an enterprise capability

This suggests the need for something broader than an agent platform.

An agent control plane is the set of capabilities through which the enterprise can identify, authorize, observe, evaluate, constrain and terminate agents participating in its work.

That does not necessarily mean one vendor or one centralized technology platform.

It means the enterprise needs a consistent control model even when execution is distributed.

“The enterprise may decentralize agent creation without decentralizing accountability.”

Teams can own agents close to their domains.

Platforms can provide shared capabilities.

Functions can retain responsibility for business outcomes.

But identity, authority and evidence need to survive across those boundaries.

The executive question

The wrong question is:

“Which agent platform should we standardize on?”

A better question is:

“What must remain consistent when the agents themselves are not?”

Identity?

Authority?

Evaluation?

Observability?

Cost?

Ownership?

Termination?

The AI native enterprise will not eliminate agent diversity.

It will need to make that diversity operable without making accountability fragmented.