<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/</link><description>Recent content on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Sat, 14 Mar 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Mission Architecture on AAuth</title><link>https://notes.karlmcguinness.com/notes/mission-architecture-on-aauth/</link><pubDate>Sat, 14 Mar 2026 09:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/mission-architecture-on-aauth/</guid><description>Mission-Bound OAuth argues for a durable Mission object that governs delegated authority across approval, lifecycle, delegation, and termination. This follow-up asks whether Dick Hardt&amp;rsquo;s AAuth draft is a better protocol substrate for the same model, and where AAuth still appears to need an explicit Mission-like authority object.</description></item><item><title>Mission-Bound OAuth</title><link>https://notes.karlmcguinness.com/notes/mission-bound-oauth/</link><pubDate>Fri, 13 Mar 2026 09:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/mission-bound-oauth/</guid><description>OAuth answers whether a request is permitted right now. Mission-Bound OAuth asks whether a delegated mission should still be running at all. This RFC proposes a durable Mission object at the Authorization Server that governs token derivation, lifecycle, delegation, and termination across agent execution.</description></item><item><title>Client Context and ID-JAG: Encoding Mission at the Authentication Layer</title><link>https://notes.karlmcguinness.com/notes/client-context-and-id-jag-encoding-mission-at-the-authentication-layer/</link><pubDate>Tue, 10 Mar 2026 09:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/client-context-and-id-jag-encoding-mission-at-the-authentication-layer/</guid><description>Rich Authorization Requests are the natural first instinct for encoding agent missions, but access tokens are audience-bound and cross-domain authorization server interoperability is limited. The OpenID Connect Client Context draft takes a different approach: encoding mission intent at authentication time so the ID Token becomes the portable trust anchor for cross-domain access via the Identity Assertion Authorization Grant pattern. Three enforcement layers result: the OpenID Provider enforces mission policy at authentication, the agent runtime enforces it before any external call, and downstream authorization servers enforce it at access time.</description></item><item><title>Standardize `act` Across Assertion Grants and JWT Access Tokens</title><link>https://notes.karlmcguinness.com/notes/standardize-act-across-assertion-grants-and-jwt-access-tokens/</link><pubDate>Mon, 09 Mar 2026 09:30:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/standardize-act-across-assertion-grants-and-jwt-access-tokens/</guid><description>The current split between token exchange semantics and JWT access token practice creates avoidable interoperability failures. A common profile for &lt;code&gt;act&lt;/code&gt;, grounded in entity profiles, can align JWT assertion grant and JWT access token processing.</description></item><item><title>Agents Don't Need Your Passport. They Need Your Authority.</title><link>https://notes.karlmcguinness.com/notes/agents-dont-need-your-passport-they-need-your-authority/</link><pubDate>Sat, 21 Feb 2026 22:59:09 -0800</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/agents-dont-need-your-passport-they-need-your-authority/</guid><description>Enterprise IAM was designed for human-paced execution. Agents remove the presence, pacing, and natural scope-limiting that made those controls work. The result is a structural gap that stronger credentials, tighter scopes, and faster JIT provisioning cannot close.</description></item><item><title>From Passports to Power of Attorney</title><link>https://notes.karlmcguinness.com/notes/from-passports-to-power-of-attorney/</link><pubDate>Sat, 21 Feb 2026 22:59:09 -0800</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/from-passports-to-power-of-attorney/</guid><description>Tokens, credentials, and scopes tell a system what an agent may do. They say nothing about why execution was authorized or when it should end. The Execution Mandate is the primitive that closes that gap: a signed, inspectable authority record that runtime systems can evaluate and revoke throughout the execution lifecycle.</description></item><item><title>Governing the Stay, Not Just the Entry</title><link>https://notes.karlmcguinness.com/notes/governing-the-stay-not-just-the-entry/</link><pubDate>Sat, 21 Feb 2026 22:59:09 -0800</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/governing-the-stay-not-just-the-entry/</guid><description>An Execution Mandate defines what delegated authority looks like. This post builds the control plane that makes it operational: how mandates are issued and held as authoritative artifacts, how authority is evaluated continuously rather than at gates, how governance crosses organizational boundaries, and where enforcement lands in practice.</description></item><item><title>About</title><link>https://notes.karlmcguinness.com/about/</link><pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/about/</guid><description>&lt;div class="profile-card"&gt;
 &lt;img src="https://notes.karlmcguinness.com/images/me.jpg" alt="Karl McGuinness" class="profile-card__photo" width="120" height="120" /&gt;
 &lt;div class="profile-card__body"&gt;
 &lt;p class="profile-card__name"&gt;Karl McGuinness&lt;/p&gt;
 
 &lt;dl class="profile-card__facts"&gt;
 
 &lt;div class="profile-card__fact"&gt;
 &lt;dt&gt;Previously&lt;/dt&gt;
 &lt;dd&gt;SVP &amp;amp; Chief Product Architect @ Okta&lt;/dd&gt;
 &lt;/div&gt;
 
 &lt;div class="profile-card__fact"&gt;
 &lt;dt&gt;Standards&lt;/dt&gt;
 &lt;dd&gt;IETF OAuth WG · OpenID Foundation&lt;/dd&gt;
 &lt;/div&gt;
 
 &lt;div class="profile-card__fact"&gt;
 &lt;dt&gt;Focus&lt;/dt&gt;
 &lt;dd&gt;Identity strategy, product architecture, agent-native world&lt;/dd&gt;
 &lt;/div&gt;
 
 &lt;div class="profile-card__fact"&gt;
 &lt;dt&gt;Currently&lt;/dt&gt;
 &lt;dd&gt;Advising identity startups&lt;/dd&gt;
 &lt;/div&gt;
 
 &lt;/dl&gt;
 
 &lt;/div&gt;
&lt;/div&gt;

&lt;p&gt;I&amp;rsquo;m &lt;a href="https://karlmcguinness.com"&gt;Karl McGuinness&lt;/a&gt;, a product and technology leader with 25+ years of experience building mission-critical, internet-scale identity and infrastructure platforms. At Okta, I spent over a decade helping modern enterprises and the broader industry treat identity as foundational infrastructure.&lt;/p&gt;
&lt;p&gt;I specialize in product architecture, the intersection of product strategy and system design. I translate ambiguous requirements into durable product structures: domain boundaries, APIs, platform extensibility, and investment sequencing that keep teams fast today and options open later.&lt;/p&gt;</description></item><item><title>Welcome to Control Plane</title><link>https://notes.karlmcguinness.com/notes/welcome-to-control-plane/</link><pubDate>Mon, 28 Apr 2025 23:22:40 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/welcome-to-control-plane/</guid><description>&lt;p&gt;Identity is getting weird again, and in a good way.&lt;/p&gt;
&lt;p&gt;This blog is where I post hot takes, field notes, and analysis on identity, security, and agentic systems. Some posts will be tactical. Some will be opinionated. Some will be me zooming out and asking, &amp;ldquo;are we solving the right problem at all?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Lately I keep coming back to one thing: most of our stack is great at deciding who can get in, and still pretty weak at governing what autonomous systems should keep doing over time.&lt;/p&gt;</description></item></channel></rss>