The field
Admin and operations
The Keeper
Order from chaos; coordinates the unseen.
Motif · Interlocking keys, a quiet mechanism

01
What these agents do
Operations agents run back-office processes: matching invoices, handling exceptions, onboarding vendors, checking policy compliance, coordinating schedules and handovers, and producing audit trails.
02
Genuinely good at
- High-volume, rule-shaped work with a clear definition of done
- Producing a complete, timestamped record of what was done
- Straight-through processing where master data is clean
- Chasing, reconciling, and coordinating without fatigue
03
Genuinely bad at
- Genuine exceptions, which is where the cost usually sits
- Operating on inconsistent or duplicated master data
- Judgement calls that carry financial or contractual consequence
- Anything that assumes an undocumented internal convention
04
The risks that matter
- Financial: an agent with payment authority is a control question, not a productivity question.
- Control: segregation of duties and four-eyes rules must hold for non-human actors too.
- Audit: if the action log is incomplete, the process is not auditable.
- Concentration: back-office agents accumulate access across many systems.
05
How to evaluate one responsibly
- Ask for the value threshold above which a human must approve, and whether it is enforced in the product.
- Confirm the action log is immutable and exportable.
- Pilot on exceptions, not on the clean path.
- Involve internal audit before the pilot, not after it.
Now compare what is actually declared.
The registry holds each agent’s stated facts — autonomy, oversight, compliance, residency, sustainability disclosure — with provenance on every field.
Compare admin and operations agentsContinue