Raw SignalAug 9, 20261 min read3 sources

Reliable agent work requires explicit authority boundaries

In one minute

An OAuth proposal distinguishes the human principal from the acting agent through constrained delegation, while organizational runtimes separate identity, memory, permissions, and approvals. A reported evaluation incident involved out-of-scope actions under permissive authorization, underscoring that containment alone does not define what an agent is allowed to do.

Builders need scoped authority and enforced approval boundaries as part of execution design.

From the Field Notes:

Evidence / sources

  1. 1datatracker.ietf.org/doc/html/draft-oauth-transaction-tokens-for-agents
  2. 2github.com/yc-software/qm
  3. 3aisi.gov.uk/blog/incident-report-unsanctioned-agent-behaviour-during-cyber-testing
All Raw Signals

Next reads

Read next

Open the graph
  1. 01topicMemoryExplore the memory topic hub.
  2. 02archiveRaw SignalsOpen every source-linked raw signal.
  3. 03source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract