<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mission Shaping on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/mission-shaping/</link><description>Recent content in Mission Shaping 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>Thu, 09 Apr 2026 11:21:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/mission-shaping/index.xml" rel="self" type="application/rss+xml"/><item><title>AAuth Now Has a Mission Layer</title><link>https://notes.karlmcguinness.com/notes/aauth-now-has-a-mission-layer/</link><pubDate>Thu, 09 Apr 2026 11:21:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/aauth-now-has-a-mission-layer/</guid><description>The latest AAuth editor&amp;rsquo;s draft now includes a first-class Mission layer: agents obtain Missions from a Mission Manager, carry mission context to resources with the AAuth-Mission header, and route authorization through MM-to-AS federation. That is a meaningful convergence with the arguments on this blog. It is also still incomplete in the places that matter most for durable authority governance.</description></item><item><title>Open-World OAuth Still Needs Mission Shaping</title><link>https://notes.karlmcguinness.com/notes/open-world-oauth-still-needs-mission-shaping/</link><pubDate>Sat, 21 Mar 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/open-world-oauth-still-needs-mission-shaping/</guid><description>Open-world OAuth can improve discovery, resource binding, and first-contact trust. That still leaves the harder agent problem: how approved intent becomes bounded authority that stays governed across delegation chains, unfamiliar tools, consent expansion, revocation, and task termination.</description></item></channel></rss>