Protocol InstituteBusiness

Feed · thread · version 3 · updated 12 October 2026

Who owns the rules when AI agents join the business?

AI agents now answer customers, spend money and approve requests, all under rules that someone has to change when they go wrong. The first report asks who that someone is. It reads 118,526 job postings, 1,167 company filings, recorded talks by 30 practitioners, 19 laws and policies, and the documentation of 31 agent products and protocols. The full report is interactive; here are the main points.

The rules live in the vendor's admin settings. In most agent products an administrator edits what an agent may do, inside the product, under a central policy. That is what the products allow. It doesn't tell us how firms decide a change.

The evidence points to existing staff running the agents, more often technical than business staff. Twenty of the thirty practitioners describe running agents themselves, and most who talk about staffing gave the work to people already on the team. In job ads, ordinary jobs list agent work almost as often as AI-titled ones do, and hiring for it still sits mostly in technology functions, not business teams.

Some of the work is missing. Supervising and tuning agents is what people talk about. Finding the unwritten rules a business already runs on, and deciding a change to them across functions, barely appear: of 771 statements, one describes finding an unwritten rule and none describes deciding such a change.

An early sign: ownership is set up front, not change by change. The analysis finds firms seem to own agent rules as standards and frameworks. Mature rule systems such as IT change also name someone to approve each specific change before it goes live. For agents the analysis found almost no one in that seat.

The law asks for overseers, not owners. From 2027, the EU AI Act and Colorado's law will require firms using AI for high-risk decisions to name people who can oversee those systems and step in. No law yet names who owns an agent's rules, and none registers agents.

The analysis suggests: write a standard for agent controls, name its owner, reserve sign-off for exceptions, and keep the vendor's console from holding the only copy of an agent's rules. The report ends with five checks you can run in your own firm in an afternoon.

The companion report, What controls do AI agent products give firms, and how are they changing?, looks at the controls themselves. Both reports are on the Research page.

These are findings of an AI-assisted analysis of public sources. Its suggestions are not a consensus view of the research group or a position of the Protocol Institute.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 7ak17qnxa54kcebqeqccmwyty9

    Quote line ![[7ak17qnxa54kcebqeqccmwyty9]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "7ak17qnxa54kcebqeqccmwyty9", "version": 3}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 3 versions