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
- Hugging Face details Moon Bot, its Slack-native coding agent with codebase and DB access — victormustar · 2026-09-05
- Computer use is now where coding agents were in Nov 2025, says agentic tooling author — austinvhuang · 2026-09-05
- Dev boosts GLM 5.2 TPS on a B300 and swaps it into Claude Code in place of Anthropic models — abhijithneil · 2026-09-05
- What forces LLM teams to optimize inference when going from MVP to production? — Ok_Philosophy_4031 · 2026-09-05
- Astra's trick: map the GUI once, then drive computer use with programmatic tool calls — anpaure · 2026-09-05
- Local Qwen 27B vibecodes a playable Godot dungeon game in just 4 prompts — jacek2023 · 2026-09-05