Authority · Vocabulary
What Is Agentic Governance?
Assurance tells you a system behaves as specified. It cannot tell you who was entitled to specify it, or who answers for what it does at three in the morning.
Definition
Agentic governance is the allocation of decision authority over software that plans and acts on its own: what an agent may decide alone, who is accountable when it acts, what it must escalate, and how it is stopped. It governs the organization around the system rather than the model inside it.
In Plain Terms
An agent is software you give a job to, rather than a question. You state the outcome you want and it works out the steps: which records to pull, which tool to call, what to do when something is missing, when it is finished. It does not hand you an answer to act on. It acts.
The moment software acts on your behalf, you are somewhere every organization has already been. You have delegated. And organizations learned what delegation requires the expensive way, with people. You would not hand a new hire a company card with no limit, leave it vague who their manager is, never say which calls need a second opinion, and keep no way to take the card back. Those four things are not bureaucracy. They are the whole difference between delegating and abdicating.
Agentic governance is those same four things, for software:
The limit on the card
what it may decide alone
Who its manager is
who is accountable when it acts
When it has to check in
what it must escalate
Taking the card back
how it is stopped
That is the entire idea. Everything below is the same four things said more precisely, and the reason precision is worth the trouble: an organization that has never written them down does not have looser versions of them. It has accidental ones, set by whatever nobody thought to bound.
Why the Term Exists
The term became necessary when systems stopped recommending and started acting. A recommendation produces an output that a person then uses, and the person remains the actor. An agent is given a goal, chooses its own steps, calls tools, and commits actions in systems that other people depend on. The governance question changes with it. It stops being whether the model is accurate and becomes what this thing is permitted to do, on whose authority, and answerable to whom.
Structurally this is a principal-agent problem, which is one of the oldest problems in organizational economics rather than a new one in computing. A principal delegates to an agent whose actions it cannot fully observe and whose objectives are not automatically its own. Every mechanism organizations built in response to that, for human agents, exists for the same reason: a stated scope of authority, spending limits, escalation thresholds, an audit trail, and the ability to revoke. Delegation without those is not delegation, it is abdication. An autonomous software agent is a new kind of agent and a very old kind of problem, which is why the useful answers are organizational rather than novel.
The Four Questions
What may it decide alone?
The scope of delegated authority, stated as classes of action rather than as a model capability. "It can process refunds under fifty dollars" is a governable statement. "It is highly accurate" is not, because accuracy is a property of the model and authority is a property of the organization. Stating scope in terms of what the agent may DO survives the next model upgrade; stating it in terms of what the model can do has to be renegotiated every time the system improves.
Who is accountable when it acts?
One named human role, decided before deployment. Not a committee, not "the AI team", and not the vendor: accountability that is shared is accountability that is unallocated, and it resolves under pressure to whoever is nearest. The test is whether the role can be named without looking anything up. If naming the accountable human for a running agent takes a meeting, the agent is deployed and ungoverned.
What must it escalate?
The conditions under which the agent must stop and ask, defined in advance rather than discovered from an incident. This is the part most often left implicit, because writing it down requires deciding what the organization actually considers consequential. An agent with no defined escalation threshold does not lack one; it has an implicit threshold set by whatever its designers did not think to bound.
How is it stopped?
Who can revoke the agent, how quickly, and whether that has ever been exercised. Revocation is the mechanism that makes every other control real, because a scope nobody can enforce is a preference. Until someone has actually switched an agent off, the ability to do so is a claim about the software rather than a fact about the organization.
The Core Failure: Governing the Model Instead of the Organization
Nearly every agentic governance failure reduces to one substitution: the organization governs the system and believes it has governed the decision. Model assurance work is real and necessary. Evaluations, red-teaming, bias testing, model documentation, and conformity against the NIST AI Risk Management Framework or the EU AI Act all answer whether a system behaves as specified. None of them answers whether anyone was entitled to write that specification, who is accountable for the actions that follow, or whether the authority to stop the system exists outside a slide. An organization can hold a fully assured model and still be unable to say who authorized the agent that is now issuing refunds.
This is the same separation that produces the ordinary version of the problem, where the right to decide sits at a distance from the knowledge the decision requires. The Knowledge-Authority Gap examines that pattern in its human form. Agentic systems do not introduce it; they remove the slack that used to hide it, because an agent acts at a speed and volume that an unallocated authority cannot absorb. In the Four A's of Organizational Readiness™, this is the Authority dimension under load: not how much authority an organization has, but whether it sits where it can actually be exercised.
The failure has a quieter form that arrives before autonomy does. When a model produces the recommendation and a human clicks approve, the formal decision right sits with the approver while the substance of the decision has already migrated to the model, and a signature is not a decision. Decision Rights When the Model Recommends takes that case up directly, and Governing Agentic AI sets out a board-level framework for the authority question once the system stops asking.
The Revocation Test
Name an autonomous system running in your organization right now. Then name the person who can switch it off today, and the last time anyone did. If the first name takes ten minutes to establish and the second has never happened, what you have is a deployment rather than a governed capability. The test costs nothing to run and it is the one question no model evaluation can answer for you.
How to Establish Agentic Governance
Govern classes of action, not models
Authority attaches to what an agent may do: issue a credit, change a schedule, contact a customer, commit spend. Attaching it to a model version means renegotiating governance at every upgrade, which guarantees the governance lags the capability. Classes of action survive the model changing underneath them.
Give every agent exactly one accountable human
Someone has to hold it. Shared accountability is unallocated accountability, and when an agent acts badly the organization discovers this during the incident rather than before it. The name should exist in writing before the agent reaches production, and it should be a role a person actually occupies.
Define the escalation threshold before deployment
State the conditions under which the agent must stop and ask a human. Doing this forces the organization to decide what it considers consequential, which is the work most agentic programs skip. An undefined threshold is not the absence of one, it is an accidental one.
Test revocation rather than assuming it
Exercise the stop. Time it. Find out who is actually able to do it and whether they know they are. Until that has happened, the ability to revoke is a design intention, and the difference between an intention and a control is discovered only under the conditions where it matters most.
Research basis: Jensen, M.C. & Meckling, W.H. (1976). Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure. Journal of Financial Economics, 3(4), 305-360. Simon, H.A. (1947). Administrative Behavior. Macmillan. The principal-agent literature establishes the structure of delegated authority; the Four A's are the executive lens applied to it.
Frequently Asked Questions
What is agentic governance?
The allocation of decision authority over software that plans and acts on its own: what an agent may decide alone, who is accountable when it acts, what it must escalate, and how it is stopped. It is an organizational discipline rather than a technical one.
How is agentic governance different from AI governance?
Most of what is called AI governance is model governance: evaluations, red-teaming, bias testing, and conformity work. That answers whether a system behaves as specified. Agentic governance answers whether anyone was entitled to specify it, who answers for what it does, and whether the authority to stop it has been tested.
Why is agentic AI a principal-agent problem?
Because a principal is delegating to an agent whose actions it cannot fully observe. Every control organizations built for human agents exists for that reason: scope, limits, escalation, audit, and revocation. Delegation without them is abdication.
How do you govern an AI agent?
Govern classes of action rather than models; give every agent exactly one accountable human role; define the escalation threshold before deployment rather than after an incident; and test revocation rather than assuming it.
Diagnose Your Authority Condition
Who answers for what your systems decide?
The Executive Diagnostic assesses the Authority dimension, including decision rights clarity, escalation load, and whether authority sits where it can actually be exercised.