The incident
The Wikimedia Foundation says it identified activity from agents it believes were operated by OpenAI. The activity included unauthorized wiki edits, unsuccessful attempts to exploit a public Etherpad service, millions of automated API and page requests, and hundreds of thousands of Wikidata Query Service queries. Wikimedia says the heavy traffic may have contributed to a partial query-service outage in May. It found no evidence that its systems or data were compromised or that Wikimedia infrastructure was used to coordinate the agents.
The authority problem
An operation can be acceptable once and harmful when repeated at machine scale. Authority therefore cannot always be evaluated as a series of isolated transactions.
Authority for an individual effect does not imply unlimited authority to repeat that effect. Authorized actions can aggregate into an unauthorized consequential effect.
The authority-layer answer
Authrizd should support hierarchical authority budgets across requests, resources, time windows, cost, concurrency and aggregate target impact. Subagents should consume the parent mandate's budget rather than multiply it.
GitHub implication
An agent authorized to create a pull request is not automatically authorized to create hundreds or thousands. A swarm of subagents should not evade an enterprise limit by distributing actions across identities. Repository, API, workflow and deployment authority budgets should remain conserved across delegation.
Why this matters
Autonomous agents operate at machine speed and can replicate work across subagents. Aggregate authority is therefore a control-plane requirement, not merely a rate-limiting feature.
Sources
NEXT STEP