Architectural analysis demonstrates the necessity of authority boundaries in agentic AI, highlighting the need for deterministic non-execution.
Identity, authentication, access control, permission, and delegation establish important facts about an AI agent, but they do not independently establish recognized authority for consequential execution. This technical response builds constructively on NIST’s discussion of identity as a foundation for agentic AI and identifies the architectural boundary that must follow identity: a determination of whether recognized authority supports the proposed execution. The paper distinguishes identity, authentication, access, permission, capability, and authority as separate system properties and introduces the Stable Authority Boundary™ as the point at which proposed execution is evaluated against recognized authority. Identity establishes who is acting. Capability establishes what can be done. Evidence establishes what can be evaluated. Authority determines whether the proposed execution may proceed. The paper further argues that strong identity is necessary, but agentic systems require an explicit pre-execution authority determination and deterministic non-execution when recognized authority cannot be established. This work is implementation-independent and does not disclose BLOCK VECTOR’s proprietary enforcement, monitoring, assessment, certification, or implementation machinery.
No takes yet. Share an insight, caveat, or question.
David Forbes (2026) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: