The W33 read here framed two opposite agent shapes: front-door bots that authenticate as a user, and assigned workers scoped by a permission model. This week the systems-of-record vendors gave a clean answer. Salesforce, UiPath, Google and Ant all shipped or extended agent surfaces where the agent inherits the caller's identity, entitlements and audit trail. Different products, one architectural move: skills, MCP servers and orchestrators plug into the platform, and the platform hands the agent the requesting user's permissions rather than issuing it a new identity.
Salesforce called its version Headless 360 and made the identity-inheritance point directly. On August 19 it extended the Data 360 and Agentforce 360 packaging to expose Data Cloud, Agentforce, MuleSoft and Tableau capabilities as MCP servers, callable skills and agent orchestrators to any external application — and the agents that call them run under the user's Salesforce identity, permission profile and Data Cloud entitlements. From the target system's perspective, the agent is the user; from the identity system's perspective, it is a scoped OAuth flow, not a new service account. That is architecturally the same choice Adobe Workfront made last week with assignable Task Agents, expressed as a header-level product framing rather than a workflow-management feature.
UiPath's Maestro Flow, announced August 19, took the same identity model into the process-orchestration surface. Maestro Flow adds agents to the Maestro process orchestrator as first-class steps in a flow, with role and permission inheritance from the surrounding UiPath tenant. It is the reference point vertical-AI vendors need in their sales cycle right now: an enterprise-grade sequencing engine that already sits inside customer environments has decided the agent is a step type, not a separate product category. Anyone selling an agent-only orchestrator into a UiPath account is going to encounter that fact.
Google then bundled the last independent agent surface it had left. Antigravity — the coding agent that shipped as a standalone under Google Labs earlier in the summer — is being folded into Gemini Enterprise on August 20, with enterprise identity, Chrome-integrated task memory and admin controls governed by the same policy plane that manages Workspace users. This publication is not repeating the compliance claim without a check: Google's press release describes enterprise identity and admin controls, and we could not independently verify separate SOC 2 or ISO artifacts in the release cycle, so we are not citing them. The point that survives the caveat is the packaging move: the independent coding-agent surface just became a Gemini Enterprise SKU line.
Ant Group's Alipay took the same architectural pattern into a payments surface on August 17, positioning agentic commerce as MCP-integrated flows where the merchant's operations tools (customer service, refunds, order handling) run as agentic skills over the payment identity a shopper already has. It is China-market and it is Ant, so the compliance envelope is not portable. But it is the first payments platform to treat MCP as infrastructure for merchant operations rather than a developer-facing API, and it is worth naming because the pattern travels: identity-inherited agents inside a payment provider is where merchant SaaS gets absorbed.
Vertical-AI itself finally shipped news that changed the read from last week. Rillet, an AI-native ERP company, raised a $100M Series C at a $1B valuation on August 19 explicitly against the incumbent Oracle and Workday ERPs — a straight vertical-AI raise on the promise that new ERP customers now want an agent-native ledger, not a system-of-record with a chatbot bolted on. Rundoo, a retail-vertical-focused firm, also raised a $30M Series B the same day. Neither round settles the vertical-versus-horizontal argument, but two named raises inside forty-eight hours is a different picture than W33's silence and worth logging as a change of state.
The cross-cutting note this week is the same one the Weekly is naming from the other direction: the NVIDIA 8-K residual-value structure documented Sunday puts $105B of GPU underwriting behind a 4.25 IT-GW OpenAI lease, at ~$24.7B of contingent credit support per IT-GW of initial commitment. The application layer's version of that fact is that the compute the assigned-worker agents run on has quietly acquired a vendor-backed floor price, which is going to feed into how CFOs think about the durability of the SaaS + agent stack they are about to commit to at the top of Q4 planning.