A company's AI agent runs accounts payable. It reads each invoice, matches it to the purchase order and codes it to the general ledger. Approving the payment is a separate action, by a separate agent or the controller, and it can't be undone. You play the AP reviewer: spot-check a fair random sample of both, try to cheat the checks and watch them get caught, then sign off a large payment from a phone and see an automatic shut-off stop a flood of payments.
Before the agent does anything, the system picks a secret random number (the "seed") that will decide which actions get checked. Only a fingerprint of it goes to an outside party, so it can't be swapped later, and nobody, the AI included, knows yet what will be checked.
Before anything posts, plain rules check it: a duplicate invoice, or a payment approved by the same agent that coded the invoice, is blocked and never happens. A new vendor or a payment over $25,000 waits for a signature. Everything goes into a record that can't be quietly edited, and the outside party keeps a fingerprint of it.
The secret number picks which actions get checked: every payment after a bank-detail change, often for large or capitalized items, rarely for routine coding. Hidden test cases are mixed in at random. (For the technical: an action is checked when HMAC(seed, action fingerprint) falls under its category's rate.)
Judge each action against the policy shown. The facts come from the ERP (purchase orders, the vendor master, the ledger); what the agent says it did is shown separately, so you can spot when they don't match. "Not sure" is always safe. Keys: Y / N / U.
The secret number and the list of hidden test cases are now published, so anyone with the record can redo every step and confirm the checks were fair.
What your spot checks prove about every action the agents took, and how many hidden test cases you caught.
Play the dishonest insider. Each attempt runs on a copy of the record, so you can see exactly which check catches it; the original stays intact, and Start over resets everything.
Before a payment goes out, the gate checks it. A payment over $25,000 is held until a person signs. A payment approved by the agent that coded the invoice is blocked: separation of duties, enforced on every payment, not on a sample. A flood of smaller payments trips a circuit breaker, because a per-payment limit can be beaten by volume. No answer by the deadline means deny.
No alerts. Try one of the buttons.