No Single Vendor Owns the Enterprise Action Layer
A placement lens for deciding where state, identity, policy, execution, evidence, and recovery should live when agents cross enterprise systems.
It is safe to place an agent only when the architecture names which system authorizes the consequential act and which evidence audit will accept. Systems of record, cloud AI platforms, model vendors, and independent gateways each control part of the path. Product breadth does not settle transaction authority.
Map the control path before the vendor
Tickets, cases, orders, employee records, and other systems that own the transaction state.
The user, agent, service, token audience, delegated chain, and current entitlement.
Purpose, object, action, limits, approval, rate, cost, and default-deny rules.
The actual write channel, receipt, result verification, recovery, and accepted audit record.
Owner, briefing, proof
Owner
The enterprise architecture and security owners decide the control point; the business process owner keeps outcome accountability.
Briefing
One cross-system action path, the candidate placements, release status, lock-in, recovery, and the authoritative system for each decision.
Proof
A drill showing authorization, denial, stop, replay, evidence continuity, and recovery across every system and protocol hop.
What leaders should take from it
Service, CRM, ERP, HCM, and work-management platforms own process state and increasingly embed agent builders, hubs, and controls.
They connect models, agents, data, identities, and tools across applications, but a connected agent is not automatically production-ready.
Tool use and computer use widen reach. The enterprise still has to define policy, receiver authorization, evidence, and recovery.
They may centralize tool identity, allowlists, and audit across platforms. The evidence does not support calling them the sole control plane.
Preview connectors, product announcements, and vendor percentage claims should not be treated as production evidence or comparative superiority.
First-party product pages establish current capability and positioning. They do not provide neutral benchmarks for operating cost, control effectiveness, portability, or customer outcomes. Workday announcement language does not prove historical general availability; Microsoft labels the inspected connections preview; SAP sample percentages are marketing estimates.
First moves before hiring anyone
Name every system, identity, protocol hop, policy decision, approval, action, evidence store, and recovery owner.
Decide which layer can refuse the transaction even when an upstream agent requests it with valid credentials.
Export policy and evidence, switch one representative path, and measure behavior delta, exceptions, recovery time, and evidence loss.
Choose one consequential action that crosses two systems of record. Compare placements on authoritative state, identity, policy enforcement, execution, evidence, recovery, release status, and lock-in.
Claim ledger
- Independent studies compare operating cost, control outcomes, and portability across native hubs, cloud runtimes, and independent gateways.
- Preview connectors become generally available and publish stable production contracts.
- Regulators or auditors establish a required authoritative agent registry or evidence store.