What happens when two agents disagree?

They do not talk to each other. The management layer holds the state, and a conflict between two agents' outputs is an exception routed to its owner, who decides.

Do we start with the whole department?

No. One workflow proves it, one role scales it, and the department is what several roles under one management layer become. The spec for each role is where each agent in the department comes from.

An agent-run department has a definite shape, and the shape still includes people

Today

One function, run on meetings and status asks

"Agent-run department" gets used for everything from one chatbot with a job title to an org chart with no people on it.
Before you decide whether it is the thing you want, you need to know what the shape actually is, and the honest description includes the people it still requires.
What follows is a reference pattern: the shape, the roles, and what it does not mean.

With agents

Several agents, one record, named people at the gates

One function runs on a record instead of on meetings.
Humans hold decisions instead of throughput.
The function is auditable without stopping it.

The shape, part by part

The pattern is function-agnostic: several agents, one operational function, one management layer, and named people holding the gates and the exceptions. Each bullet describes one part of the shape.

Several agents each own one workflow of the function

Intake, processing, close, reporting: each workflow has its own spec, its own gate and its own readiness status, and each spec comes from the same method that turns a role into an AI Employee spec.

The management layer holds the work orders

It assigns, sequences, records state and hands work between agents. No agent talks to another outside the record, and How It Works describes the work order the layer holds.

Every hand-off between agents is a recorded state change

That is what makes the function auditable end to end: the audit trail is the record of the work, written as the work happens.

Human gate

Gate-holders are named people, one per consequential step in the function. Nothing irreversible happens without their sign-off, and the management layer routes to them with the evidence attached. The approval gates entry defines the gate they hold.

Exception owners are named people who receive what the rules cannot decide

Escalation is a route with an owner, and an exception arriving at its owner is the system working as designed.

The function's recurring work runs as routines, and its changes run as plans

Routines carry cycle sign-off; plans carry phase gates. The plans and routines entry defines both shapes.

The management layer reports on the function from the record

State, open exceptions, gate decisions. Oversight reads the record rather than asking the agents how it is going.

Results

What changes when the function runs on a record

A status that is a query

Every hand-off and decision is a state change in the management layer, so the status of the function is a query rather than a conversation.

People hold the decisions

Gate-holders and exception owners are named roles at named steps, so the people in the function are there for judgement and sign-off.

Auditable without stopping

The record is the audit trail, written as the work happens, so reviewing the function does not mean pausing it.

Where this fits

Department / AI Department

This is the AI Department tier, reached through the AI Department door, and this page describes the shape rather than an engagement. The rung below is the AI Employee: one role's worth of process work, specified and gated, and a department is what several of those become under one management layer. The finance and operations back office entries are the per-function instances of this pattern. How It Works describes the work order protocol and the gates the whole function runs under.

Tier 3 / Transform

How It Works

Questions, answered

The gate-holders and exception owners the function's consequential steps require. The count comes from the function's spec, from which steps are consequential and which exceptions need an owner, rather than from a ratio.

AI Opportunity Audit

Draw the shape for one function

Bring the function you would redesign first and map which steps a person must keep.

Book an audit