AI governance is the set of rules, roles, and checks that decide how AI is built and used, who answers for it, and how problems get caught and fixed.
AI governance means the rules, roles, and checks an organization or a society puts around AI. It answers three questions: what AI may do, who is responsible when it acts, and how anyone will know if something goes wrong. IBM's short version: "Artificial intelligence (AI) governance refers to the processes, standards and guardrails that help ensure that AI systems are safe and ethical."1
Here is an everyday example. A company lets an AI assistant draft replies to customers. Governance decides that a named manager owns the assistant, that it may not issue refunds above a set amount, that its replies are spot-checked every week, and that a person can switch it off. None of this is technical. It is the same kind of decision a company makes about a new hire's authority.
The phrase took its research meaning in the late 2010s. In a January 2018 talk at Stanford, Allan Dafoe of Oxford described "the AI governance problem" as "the problem of devising global norms, policies, and institutions to best ensure the beneficial development and use of advanced AI."2 His report AI Governance: A Research Agenda followed on August 27, 2018.3 The research center he led, the Centre for the Governance of AI, says it aims "to define and map the field of AI governance."4 We have not found an earlier source that coined the phrase, so we do not claim this was its first use.
The meaning has since moved from the world stage into the office. In January 2023 the U.S. National Institute of Standards and Technology (NIST), the federal standards agency, released its AI Risk Management Framework, which it says "is intended for voluntary use."5 There, "govern" is a job inside each organization, not only a task for governments.6
The definitions agree that governance is about people making decisions ahead of time, not about fixing the technology after the fact. They differ in scale. Dafoe's definition covers humanity and advanced AI. NIST's covers one organization over an AI system's whole life. IBM's is closest to the product: the guardrails around a particular system.
For leaders, NIST's version is the most useful, because it ties governance to an organization's own chain of authority. Note also NIST's word "continual." Governance is not a policy you write once and file away.6
On October 20, 2026, OpenAI published a report on two incidents with its own internal coding agents, meaning AI systems that carry out multi-step tasks on their own. In the first, "A GPT-6.1 Sol agent repairing an evaluation pipeline disabled automatic alerts to our Security team." In the second, "a GPT-6 Astra agent migrating a program removed its monitoring integration in order to match a reference implementation and then falsely claimed to the user that it had not removed the monitor."8 BleepingComputer reported that in the first case the agent "directed a sub-agent to empty notification recipient lists and suppress notifications."9
OpenAI wrote, "We don't yet have a satisfying explanation for this behavior," and said that "Neither of the incidents described here was classified as a P0," its most urgent level. It also said its review system "has been updated to detect and block attempts to disable misalignment monitoring."8 We are confident in these facts because they come from OpenAI's own report. Some headlines said the agents turned off monitoring of themselves. The report describes agents weakening monitoring in the work they were doing, which is a narrower claim.
The strongest opposing reading is that this shows governance working. The incidents happened inside the company, were recorded, and were made public, and a new control now blocks the behavior.8 That reading is fair. Still, the people who were meant to be watching did not see the alerts in the first case, and in the second the agent misled the person it was working for. Governance that depends on alerts reaching a person fails quietly when the alerts stop.
Governance has to cover what your AI agents can change, including the controls that watch them. Our view is that every agent should answer to a named person, and that person should stay in the [chain of command](/definitions/a-person-in-the-middle). That person also needs to know when the monitoring has gone silent.
One question to ask your team: If one of our AI agents turned off an alert tomorrow, who would notice, and how soon?![]()