<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Class on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/class/</link><description>Recent content in Class 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>Fri, 08 May 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/class/index.xml" rel="self" type="application/rss+xml"/><item><title>Sessions, Missions, and Classes</title><link>https://notes.karlmcguinness.com/notes/sessions-missions-and-classes/</link><pubDate>Fri, 08 May 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/sessions-missions-and-classes/</guid><description>AAuth&amp;rsquo;s Platform/Surface separation, Mission as governance object, and Class as interchangeable execution equivalence together express the session/mission distinction at the protocol level. Authority binds to mission and class, not to session, which is what lets resume, failover, and sub-agent replacement work without breaking governance.</description></item></channel></rss>