<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-World OAuth on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/series/open-world-oauth/</link><description>Recent content in Open-World OAuth 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, 21 Mar 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/series/open-world-oauth/index.xml" rel="self" type="application/rss+xml"/><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><item><title>OAuth for Open-World Ecosystems</title><link>https://notes.karlmcguinness.com/notes/oauth-for-open-world-ecosystems/</link><pubDate>Fri, 20 Mar 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/oauth-for-open-world-ecosystems/</guid><description>OAuth was built for closed worlds, and that constraint is why it became mature. Agents expose the limits of that deployment model. This post traces what the newer OAuth standards get right and which substrate gaps still need to close.</description></item></channel></rss>