Tags

64 Tags

Authorization

64 posts
  1. The Mission Extension for PAP 1.0 A mandate the company holds, on the wire, with tests
  2. Super-Agents Need Missions Reading DeepSeek's Super-agent Design for Authority
  3. AuthZEN and the Blueprint: Reference The Full Gap Map, the Two-Vendor Refund Test in Writing, and the Detail Behind Each Part
  4. Canceling One Task Without Stopping the Agent The Decision Contract Still Needs a Shared Record of Approved Work
  5. The Gateway Should Not Own the Approval How the AuthZEN Workstreams Meet the Blueprint Alliance at the Tool Call, the Approval, and the Token Endpoint
View all 64

AuthZEN

22 posts
  1. AuthZEN and the Blueprint: Reference The Full Gap Map, the Two-Vendor Refund Test in Writing, and the Detail Behind Each Part
  2. Canceling One Task Without Stopping the Agent The Decision Contract Still Needs a Shared Record of Approved Work
  3. The Gateway Should Not Own the Approval How the AuthZEN Workstreams Meet the Blueprint Alliance at the Tool Call, the Approval, and the Token Endpoint
  4. Your Agent Gateway Should Not Choose Your Policy Engine Why the Blueprint Alliance's Fleet of Enforcement Points Needs AuthZEN as Its Fifth Standard
  5. Agent Authority Has No General System of Record The Third Control Point Is the Approved Task, and Its General Record Does Not Exist Yet
View all 22

Delegated Authority

19 posts
  1. A Blocked Agent Is a Captive Client
  2. Continuity Is Not One Thing The Four Questions of Delegated Work, and the Invariants That Compose Their Answers
  3. Common Objections to Mission-Based Authorization Answers for the People Who Run Today's Control Planes
  4. The Question Authorization Never Answered A History of Delegated Authority, from Passwords to Missions
  5. Answering the Laws of AIdentity A Critical Crosswalk from Patrick Parker's Seven Laws to Mission-Bound Authorization
View all 19

IAM

30 posts
  1. CIMD Anchors the Client. A Software Statement Vouches for It. Domain Control, Portable Review, and the Runtime Question Both Leave Open
  2. Continuity Is Not One Thing The Four Questions of Delegated Work, and the Invariants That Compose Their Answers
  3. The Continuity Evaluation Kit A Vocabulary, a Rubric, and a Living Map for the Four Questions
  4. Mission-Bound Authorization: The Glossary The Handbook's Vocabulary, A to Z
  5. The Mission-Based Authorization Vendor Test Six Questions for Anyone Claiming Agent Authorization
View all 30

Intent-Based Authorization

9 posts
  1. Mission-Based Authorization: The Field Reference The Category, the Litmus Test, the Landscape, and the Running Example
  2. The Agent Runtime and Audit Sessions Are Not Authority, Safe Unwinding, and Tamper-Evident Evidence
  3. Mission Lifecycle and Change Observe, Revoke, Grow, Complete
  4. Mission-Bound Runtime Enforcement From Mission-Bound Tokens to Mission-Bound Actions
  5. Mission-Bound Authority: Instances, Actors, and Delegation From Authenticated Agent Identity to Bounded, Narrowing Authority
View all 9

Internet-Draft

19 posts
  1. CIMD Anchors the Client. A Software Statement Vouches for It. Domain Control, Portable Review, and the Runtime Question Both Leave Open
  2. Client Instances Aren't Actors Either
  3. Mission-Bound Authorization: The Standards Map OAuth, WIMSE, and OpenID, Mapped to the Architecture
  4. Mission-Bound Authorization on the Wire The Q3 Board Packet, Exhibit by Exhibit
  5. Mission-Based Authorization: The Field Reference The Category, the Litmus Test, the Landscape, and the Running Example
View all 19

Interoperability

9 posts
  1. An Agent Is Not Its OAuth Client Agent Principal Profiles: One Agent Across Platforms and Resource Domains
  2. Canceling One Task Without Stopping the Agent The Decision Contract Still Needs a Shared Record of Approved Work
  3. Your Agent Gateway Should Not Choose Your Policy Engine Why the Blueprint Alliance's Fleet of Enforcement Points Needs AuthZEN as Its Fifth Standard
  4. The Runtime Mints the Identity. That Does Not Make It the Authority. The Agent Identity Market Will Be Decided at the Binding Layer
  5. Agent Authority Has No General System of Record The Third Control Point Is the Approved Task, and Its General Record Does Not Exist Yet
View all 9

MCP

12 posts
  1. The Gateway Should Not Own the Approval How the AuthZEN Workstreams Meet the Blueprint Alliance at the Tool Call, the Approval, and the Token Endpoint
  2. Your Agent Gateway Should Not Choose Your Policy Engine Why the Blueprint Alliance's Fleet of Enforcement Points Needs AuthZEN as Its Fifth Standard
  3. Kerberos Won Because Nobody Had to Implement It The SSPI Question for Agent Authorization
  4. The MCP Lesson Running Code Creates the Wedge. Governance Consolidates What Survives.
  5. Cross App Access Shows How the Layered Play Ships The MCP Extension Is Stable. The First Loop Is Live. The Partner Ecosystem Is Still Rolling Out.
View all 12

Mission-Bound Authorization

29 posts
  1. The Mission Extension for PAP 1.0 A mandate the company holds, on the wire, with tests
  2. Super-Agents Need Missions Reading DeepSeek's Super-agent Design for Authority
  3. AuthZEN and the Blueprint: Reference The Full Gap Map, the Two-Vendor Refund Test in Writing, and the Detail Behind Each Part
  4. Canceling One Task Without Stopping the Agent The Decision Contract Still Needs a Shared Record of Approved Work
  5. A Mission the Company Can Check An Extension Proposal for the Personal Agent Protocol
View all 29

Security Architecture

12 posts
  1. The Mission-Based Authorization Vendor Test Six Questions for Anyone Claiming Agent Authorization
  2. Containing the OWASP Agentic Threats Seventeen Agentic Threats and the LLM Top 10, Each Given a Verdict
  3. Splitting the Lethal Trifecta How Mission-Bound Authorization Bounds the Defining Agent Threat Model
  4. Canceling the Card Doesn't Stop the Charges Endings, Unwindings, and the Statement That Reconciles It All
  5. The Network Approves Every Transaction, Not the Card Per-Action Authorization, and the Escape Hatch Called Cash
View all 12

Standards

28 posts
  1. The Mission Extension for PAP 1.0 A mandate the company holds, on the wire, with tests
  2. An Agent Is Not Its OAuth Client Agent Principal Profiles: One Agent Across Platforms and Resource Domains
  3. CIMD Anchors the Client. A Software Statement Vouches for It. Domain Control, Portable Review, and the Runtime Question Both Leave Open
  4. Client Instances Aren't Actors Either
  5. AuthZEN and the Blueprint: Reference The Full Gap Map, the Two-Vendor Refund Test in Writing, and the Detail Behind Each Part
View all 28