<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Weighing Mission-Bound Authorization on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/series/weighing-mission-bound-authorization/</link><description>Recent content in Weighing Mission-Bound Authorization 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, 10 Jul 2026 19:20:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/series/weighing-mission-bound-authorization/index.xml" rel="self" type="application/rss+xml"/><item><title>The Convergence and the Wagers</title><link>https://notes.karlmcguinness.com/notes/the-convergence-and-the-wagers/</link><pubDate>Fri, 10 Jul 2026 19:20:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/the-convergence-and-the-wagers/</guid><description>The handbook closes on judgment. First the strongest outside evidence: AAuth, the proposed clean-slate agent protocol, independently grew a first-class mission layer in its 01 revision, an independent derivation landing on the same missing object. Then the honest bets: admission grain, issuer home, the price of Termination, the necessity of the object itself, and the portability of its authority, each stated with the evidence that would falsify it. The laws and the claim gate are the invariants. The admission grain, the issuer home, the price of Termination, the necessity of the object itself, and the portability of its authority are the wagers, and deployment experience, not this handbook, will settle them.</description></item><item><title>The Authority Control Plane</title><link>https://notes.karlmcguinness.com/notes/the-authority-control-plane/</link><pubDate>Fri, 10 Jul 2026 19:10:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/the-authority-control-plane/</guid><description>Issuance gating and runtime enforcement are two independent chokepoints, strictly stronger together: a gap in PEP coverage is still bounded at the token layer, and an outstanding token is still stopped at the action layer. The Mission Authority Server, the issuance grant, the Mandate, and Cross-Domain Projection extend the pattern space. And the structural reading platform engineers reach for unprompted: the layer is the control plane for delegated authority, mapped concept by concept from desired state to the fleet API, with the disciplines that keep the framing honest.</description></item><item><title>What Survives Without OAuth</title><link>https://notes.karlmcguinness.com/notes/what-survives-without-oauth/</link><pubDate>Fri, 10 Jul 2026 19:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/what-survives-without-oauth/</guid><description>OAuth is the flagship binding because it is deployment reality, but the model does not depend on it. This part states the framework the profiles realize: four functions (compilation, projection, containment, continuity), a verb spine of nine verbs from propose to analyze, and the fundamental-versus-accidental test. Which ideas survive if OAuth disappears? Nearly all of them: the layer, the laws, the vocabulary, the approved task with an integrity-anchored record, approval evidence, runtime containment. What is accidental is the realization: PAR, RAR, the claim names, the wire shapes.</description></item></channel></rss>