Keeping humans in command
The rules that keep an agent answerable — built in, not watched over. This module is the everyday face of governance: how authority over an agent holds whether or not anyone is looking.
5.1 Command is structural, not vigilance
You cannot keep humans in command by watching an agent every minute; no one has the attention for it, and the moment you look away is the moment it matters. Command has to be built into how the agent works — so the human authority holds whether or not anyone is looking.
5.2 The gate
The first piece is a gate: certain actions — those that touch people, money, or anything irreversible — always route to a human, by a rule the agent cannot route around. Not a setting that can be switched off under pressure, but a boundary in the structure. An agent that can be talked past its own limits is not under command.
5.3 The record
The second piece is a record: every step the agent takes, logged, so that later you can answer the question that decides every dispute and audit — who decided this, on what basis, and when? An action you cannot account for afterwards is one you were never truly in command of.
5.4 The constitution
Underneath both is a written floor — the things that always need a human, the lines that are never crossed — set by you and changed only in the open, never by the agent quietly drifting. The learning part of the tool sits under that floor. When you change a rule, you change the rule, in plain sight, not the machine's hidden workings.
5.5 The ground it runs on
An agent is only as answerable as the ground it runs on. Whose infrastructure holds your records, and whose rules the tool ultimately serves, decides who it really answers to. Whose infrastructure, whose jurisdiction, whose AI — a tool on someone else's cloud answers, in the end, to them. Command is not only about the gate and the record; it is about where the whole thing stands. A course that left this out would be leaving out the foundation.
Discussion topics
- For one task you'd give an agent, what is the rule that must always route to a human — and where is the record if the decision is questioned a year from now?
- Whose terms govern the tools you already use — and could those terms change without your say?
5.6 This is governance
Keeping humans in command is the everyday face of governance. The companion Village Governance Course goes deeper on the instruments named here — the record that can be relied upon, the constitution, the decision that can be demonstrated after the fact. The two courses are halves of one discipline. Command is not control of every step; it is the built-in authority to stop what should not proceed, and to account for what did.
Further reading
- The off switch is not enough — why command over an agent must be structural, not a button.
- A control tower, not a watchtower — the shape of oversight that actually holds.
- Tamper-evident governance — the record that can be relied upon afterwards.
- Village Governance Course — the companion course on the record, the constitution, and the demonstrable decision.
Questions by role — not by rank
Grouped by role, not by rank — and the roles are flattening: in a small business one person often holds several, and in a one-person-plus-agents business, one person holds them all. Command holds only if the gate, the record and the floor are visible to everyone the agent's actions touch.
(a board, the owners — or you.) Whose infrastructure, jurisdiction and rules does our tool ultimately answer to — and who sets the written floor it can never cross?
(whoever runs the change — or you.) Build the gate and the record into how the agent works, not into a promise to watch it; change the constitution only in the open.
(team leads — or you.) For each task you'd give an agent, what is the one rule that must always route to a human — and where would the record be a year from now?
(the people closest to the task — including the newest.) You can contribute: flag where a boundary is missing, or where the agent could be talked past its limits. You're entitled to see: the record of who decided what, and the floor that stands behind your work.
Self-check
1. Why is "we'll keep an eye on it" not a real control?
The moment you look away is the moment it matters; the gate must be built in.
2. What is the record for?
An action you cannot account for afterwards is one you were never truly in command of.
3. Why does "the ground it runs on" belong in a course about command?
Command is also about whose infrastructure, jurisdiction and rules the whole thing stands on.