https://notes.karlmcguinness.com/series/designing-mission-bound-authorization/Recent content in Designing Mission-Bound Authorization on Control Plane by Karl McGuinnessHugoen-uspublic@karlmcguinness.com (Karl McGuinness)public@karlmcguinness.com (Karl McGuinness)Fri, 10 Jul 2026 19:30:00 -0700https://notes.karlmcguinness.com/notes/adopting-mission-bound-authorization/Fri, 10 Jul 2026 19:30:00 -0700public@karlmcguinness.com (Karl McGuinness)https://notes.karlmcguinness.com/notes/adopting-mission-bound-authorization/A definitive architecture that ends without a build order is a tour, not a blueprint. Most estates start at the read-only ceiling: agents capped at read access, humans approving or executing the writes, and pilots that never graduate. This closer names what that posture costs and stages the way off it: crawl by shipping the issuance core (approved, integrity-anchored Missions and a possession-independent kill switch, honestly labeled governance rather than safety), walk by adding the protocol MVP (per-action enforcement, the AuthZEN binding, and Status freshness, all on substrate that already shipped), and run by climbing to the Governed and High-Assurance Agent levels, each of which makes a broader class of write authority defensible. Plus the ecosystem to compose with, the five operational surfaces you will own, and the pieces the community still has to standardize.https://notes.karlmcguinness.com/notes/the-mission-is-the-missing-abstraction/Fri, 10 Jul 2026 10:00:00 -0700public@karlmcguinness.com (Karl McGuinness)https://notes.karlmcguinness.com/notes/the-mission-is-the-missing-abstraction/The AI agent auth best-practices draft names the Mission and declares its translation into authorization out of scope. This is the core argument on the other side of that line: why the approved task is the missing object above authentication and instance identity, how the argument converged, the Mission-versus-Intent boundary, and where to start. The definitions, object model, lifecycle, and glossary live in the Reference.https://notes.karlmcguinness.com/notes/from-the-card-to-the-architecture/Fri, 10 Jul 2026 09:45:00 -0700public@karlmcguinness.com (Karl McGuinness)https://notes.karlmcguinness.com/notes/from-the-card-to-the-architecture/What the Corporate Card Already Solved walked a working delegated-authority architecture one control at a time and never mentioned a protocol. This part is the joint between that mental model and this chapter’s architecture. The five rules the card world taught become the five laws of delegated authority, stated for any substrate. The corporate-card test becomes the claim gate a vendor claim must pass. And the build lists that closed each card post, the things the agent stack cannot borrow from the expense world, turn out to enumerate the draft family: disclosure integrity, field-speed narrowing, checkpoints per boundary, endings that propagate, and a record that earns trust without a bank.