Chapter Eight / Step Five
Operate
Your team approves what runs. The record assembles itself as a byproduct.
The proof assembles itself. Nobody types it after the fact.
Why it matters
Otherwise you spend as much time proving the work as doing it.
An agent that does useful work and keeps no record of it leaves you reconstructing that work later from email and memory. The reconstruction costs more senior time than the work saved.
What good looks like
The agent runs the process. It surfaces exceptions for human review. Your team approves what needs approval. Every action is logged with a timestamp, the data it referenced, the rule it applied, and the decision made. When someone asks, your board, a client, a regulator, an acquirer, the proof is already assembled. You share it. No scramble.
The work, the logging, and the flagging of anything unusual.
The judgment calls, and the approval that puts a name on the record.
That division is what makes the trail real. The agent cannot approve its own work. Your team cannot be asked to log it by hand.
Figure 8.1
The trail writes itself.
Monthly vendor payment run, 847 invoices. Nobody typed any of this.
In your firm
Your board asks how you know the agent did what you said it would, on every payment, for the last six months. You have the work. You cannot show the working.
With the record running, you export it: every check timestamped, every exception flagged, every approval named. None of it was written after the fact.
The work was done correctly. That is not the same as being able to show it.