<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Conformance on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/conformance/</link><description>Recent content in Conformance 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, 06 Jun 2026 17:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/conformance/index.xml" rel="self" type="application/rss+xml"/><item><title>Mission-Bound Authorization Conformance</title><link>https://notes.karlmcguinness.com/notes/mission-bound-authorization-conformance/</link><pubDate>Sat, 06 Jun 2026 17:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/mission-bound-authorization-conformance/</guid><description>Conformance to Mission-Bound Authorization is described along three complementary axes: the six-level Conformance Ladder, the four-tier Resource Server scale, and the three-tier Compliance scale. This post defines valid combinations and shows what each level looks like on OAuth-only, AAuth-only, and cross-substrate deployments.</description></item></channel></rss>