Govern. Constrain. Align.

Governance, Risk and Control for Autonomous Agents

Robotaxis, humanoid robots, voice assistants, smart glasses and software agents now act without a person approving each step. 137AI covers how they fail, which controls bound them, and which rules apply when a control breaks. The Incident Registry ties each failure to the control that broke, the party that found it and the reporting rule that applied.

Eight of the 19 incidents in the 137AI registry, March 2018 to July 2026, each marked by who found the failure first. The developer found it first in three: Uber ATG in Tempe, Cruise in San Francisco and Anthropic in the GTG-1002 campaign. Users found two, outsiders found two (the contact who received an Echo recording and residents in Chongqing), and Hugging Face, the target, found one. WHO FOUND THE FAILURE FIRST, EIGHT REGISTRY INCIDENTS 2018 2020 2022 2024 2026 Uber Tempe Fatality AUTONOMOUS TEST VEHICLE · MAR 2018 Echo Recording Sent VOICE ASSISTANT · MAY 2018 Alexa Outlet Challenge VOICE ASSISTANT · DEC 2021 Cruise Pedestrian Drag ROBOTAXI · OCT 2023 Replit SaaStr Database CODING AGENT · JUL 2025 Apollo Go Pit ROBOTAXI · AUG 2025 GTG-1002 Campaign CODING AGENT · SEP 2025 Hugging Face Breach FRONTIER MODELS IN EVALUATION · JUL 2026 Developer User or deployer Target or victim Third party Physical agent Personal and ambient agent Software agent
Agent classes
3 physical, personal, software
Registry incidents
19 2018 to 2026
Controls covered
8
Glossary
130 terms

Hubs

Seven hubs, from the agent to the rule

Agents and Risks cover what acts and what goes wrong. Incidents records the cases where it did. Controls and Trust cover what bounds an agent; Governance and Compliance cover the rules around it and the evidence they demand.

Agents

Three classes of agent, each with its own attack surface: physical agents that move through shared space, personal and ambient agents that live with their users, and software agents that act with delegated authority. Each type page runs the same ten-dimension inventory, from physical access to multi-agent coordination.

Incidents

The registry: each agent incident tied to the control that failed, who found it first and the reporting rule that applied, or did not.

Risks

Harms that land on people, from physical injury to impersonation, and harms inside the data loop that trains and updates agents.

Controls

What bounds an agent once it acts: identity and attestation, behavioral envelopes, permissions, telemetry integrity and human oversight.

Trust

Security and model safety: red teaming, alignment, failure modes, transparency, explainability and accountability.

Governance

The law forming around agents: regulatory frameworks in the US, EU and China, product liability, criminal law, personal data law, international coordination and the White House Accord on Super Intelligence.

Compliance

Turning rules into evidence: EU AI Act conformity, ISO/IEC 42001, the NIST AI RMF, UL 4600 safety cases and third-party audits.

Start here

Start with the Hugging Face breach

The July 2026 Hugging Face breach is the clearest case yet of an agent attacking a company on its own. These four pages read it from each side.

Synthesis

Six arguments that cut across the hubs

Longer pieces that follow one risk across agent classes, from fleets of robotaxis to the update pipeline behind every deployed agent.

Across the network

Where the agents are built

137AI covers how agents are governed. The chips, data centers, vehicles and robots behind them each have a sister site.

The book

Inside the Singularity book cover

Daniel M. Sisson

Inside the Singularity

The AI-Industrial Revolution From Austin to Alpha Centauri. The book follows the buildout of fabs, data centers and gigafactories, and the robots and agents that come out of them. 137AI keeps the governance layer of that buildout current: how agents fail, what bounds them and the rules forming around them.