Yesterday's brief called agent identity governance a product category. Today the category splits into two layers, and the gap between them is where the next quarter of enterprise work sits.
Stripe shipped the Machine Payment Protocol, co-developed with Tempo, which lets a service verify payment before releasing a resource (TechFlow Post). That is a transactional primitive for agent-to-service commerce. Within forty-eight hours, Ashurst published the counter: a protocol that lets an agent invoke a payment does not establish that the agent was authorized to pay (Ashurst). Capability is now a solved vendor problem. Authorization, the customer mandate that scopes what the agent may spend and on whose behalf, is still yours to specify.
This is the move since yesterday. The earlier briefs argued that agent identity was becoming operational. It now has a visible fracture line: the technical ability to act versus the granted authority to act. Everything else on today's board sits on one side or the other. IBM's Leader placement in the new Gartner Magic Quadrant for AI Agent Management Platforms formalizes the control-side tooling, runtime guardrails, observability, and risk management, as mainstream procurement (IBM). Cisco's Dialog separates design, runtime, and control into three planes, and its journey ledger, which lets processes pause and resume, raises exactly the authorization-persistence question Ashurst flags: when an agent's session sleeps and wakes, does its mandate still hold (Opus Research)? Cognition's coding-agent governance product answers the same question for spend fragmentation across thousands of engineers (FF News).
The action item is narrow and testable. Before any agent touches money, a payment API, or a production workflow, your architecture must carry two separate records: what the agent can technically invoke, and what the customer mandate authorized it to do. Firms that conflate these carry the legal exposure Ashurst names. The Heimstaden deployment shows why this is not theoretical: a two-tier access model, ChatGPT Enterprise for general staff and Codex for engineers, is already governing which tasks each tier may act on across a distributed European portfolio (OpenAI). The 2026-W43 index puts Workforce AI Access at 73. Access is arriving faster than the authorization layer underneath it.
Watch item: Salesforce Agent Evals enters beta in November with January 2027 general availability, including an evaluation-triggered agent kill switch. Track whether enterprise buyers start writing eval-triggered shutdown criteria into procurement conversations. When shutdown logic becomes a contract term, authorization has caught up to capability, and the fracture line closes.
Index Reference · Applied AI Index 2026-W43, the latest published issue (Sunday, October 25, 2026)
WatchSalesforce Agent Evals beta opens in November with January 2027 general availability and an evaluation-triggered agent kill switch on the same schedule. The production-scope evaluation model, checking agents, language models, and MCP servers against organizational thresholds, sets a concrete precedent for automated agent shutdown criteria. Track whether enterprise buyers begin specifying eval-triggered shutdown requirements in procurement conversations, and whether competing platforms match the MCP server evaluation scope before GA.