Authority as a first-class primitive: why agents need portable, verifiable permission objects
DogInteresting8548 · reddit · 2026-09-05
As agents move from generating information to taking real actions (transferring funds, deploying infrastructure, spawning sub-agents), the author argues the industry has primitives for API calls, identity and access — but no general-purpose primitive answering "is this action permitted, and on whose authority?"
The proposal: represent the authority to act as a portable, verifiable object instead of reconstructing permission checks inside every system an agent touches.
- Calls like nomos.can({authority, action: "transferfunds", facts: {...}}) return AUTHORIZED / DENIED / ESCALATED
- Architecture shifts from Agent → Tool → Permission Check to Agent → Authority → Action
- Authority can be delegated down an Organization → Department → Agent → Action chain
The author invites the community to point out where the model breaks.
More from coding & agent
- 105 Real Bugs Tested: GPT-6.1 Sol Over 10x Cheaper Than GPT-5.6 Sol — PawelHuryn · 2026-10-23
- Dev builds SkiFree-style sled game in one prompt, praises DeepSeek Flash — victormustar · 2026-10-23
- Every ditched personal agents for a shared Claude Managed Agents coworker in one week — every · 2026-10-23
- WorkOS shows how to let AI agents safely sign up for your app with auth.md and ID-JAG — AI Engineer · 2026-10-23
- Devs on Reddit swap tactics for stopping prompt regressions in AI agents — SleepFlimsy6963 · 2026-10-23
- Claude Code + ComfyUI MCP workflow for client work: paid models or open weights? — newaccount47 · 2026-10-23