Mission shaping
Mission Shaping Problem · Mission Proposal · Approved Mission · Mission Authority Model
In Karl McGuinness's Mission-Bound OAuth framework, the step that turns a human's approved intent into a machine-readable authority artifact for policy engines. It comes before authorization, not instead of it.
In our briefings
The claim each of the newest briefings on Mission shaping would have you leave with.
A person's approved request is not, by itself, authority an agent can be held to, McGuinness argues, and relatively few deployments perform the step that would make it one. That step converts approved intent into a bounded authority artifact an enforcement point can evaluate. By his account, many systems instead fall into one of five patterns: scope enumeration, app-local mapping, LLM-generated requests, broad standing authority with prompt discipline, or a formal policy language. He says the most common land in the third or fourth, and that where nothing makes the conversion, the agent's own judgment becomes the effective policy engine. This is one author's argument, but two production designs we have read fit it. Uber's agent tokens carry the full chain of who asked through every hop, and Sierra's gateway runs interactive agent work as the user, with that person's permissions. In our reading, neither records what the person approved.
A user's approved request is not yet authority an agent can be held to, and most deployments skip that stepBI-FIND-2026-0202
A delegated mission's authority must be a subset of the parent's, McGuinness argues, and OAuth token exchange (RFC 8693) does not guarantee it. Token exchange carries the delegation, but he calls enforcing the narrowing implementation-dependent and not a protocol guarantee. He writes that in production token exchange deployments today, child tokens routinely inherit the parent's full scope unless the implementation explicitly narrows them, so agents compound a failure that OAuth delegation already has. A child agent may also run in a different runtime or expose weaker telemetry, so authority that is narrower on paper can be less governable in practice. He proposes that the mission's state owner rate each hop's trust quality, meaning how well that hop can be observed and checked, and give a low-rated child a more conservative budget. For a sub-agent an orchestrator spawns at runtime, he says the state owner must still issue its authority, but asks what triggers that issuance. Our briefing on Uber's production design found a token chain that records each agent hop without describing any narrowing. Our briefing on Highflame's open-source ZeroID found narrowing by scope intersection offered as an explicit step.
OAuth token exchange does not guarantee a sub-agent stays inside its parent's accessBI-FIND-2026-0228
McGuinness says the first problem for a SaaS product manager is that "my app only understands users": every user needs a subscription plan and a SKU, and nothing says which one an agent gets. So the agent is provisioned as a human, with code added to hide that it is an agent. He traces the gap to authorization debt: apps enforced access through the screens they showed, so few built fine-grained authorization, and once the agent takes over the app layer the app cannot be relied on to enforce. The gateways now shipping are, in his words, "better than not having it", but he expects them to hit the same limits as the Zscaler proxy model: a tool-call policy without the app's domain model.
SaaS apps that only know users end up giving agents human accounts, says Okta's former chief architectBI-FIND-2026-1434
Cited in 5 briefings
Every briefing that discusses this term, newest first.
- A user's approved request is not yet authority an agent can be held to, and most deployments skip that step
Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 17, 2026
- OAuth token exchange does not guarantee a sub-agent stays inside its parent's access
Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 18, 2026
- SaaS apps that only know users end up giving agents human accounts, says Okta's former chief architect
Podcast · · The Identity Jedi Show: Where Identity Meets Strategy · Agents need a mission, not a key. · Oct 21, 2026
- Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reach
Draft · · IETF Internet-Draft (individual submission, since adopted by the WIMSE working group) · Pieter Kasselman et al. · Jul 6, 2026
- On its authors' tasks, an LLM check of agent scopes works at one tool and refuses most valid three-tool requests
Paper · · arXiv · Majed El Helou et al. · Oct 30, 2025