Brightline's payment run, behind the screen

In One job, start to finish you read the brief for Brightline Wholesale Supply's Friday payment run. The AI Worker marks each invoice due in the next seven days pay, hold or ask, and its total must match the checking program's total. Now say Brightline turns that brief into a scheduled task that runs every Friday morning. Here is what keeps it safe behind the screen.

Problem 1: the desk is replaced while it checks invoice 8, for example after a crash. If the AI Worker kept its notes only on the borrowed desk, the work would be lost. So the task saves each decision to a progress list off the desk, the moment it decides. When the work starts again on a fresh desk, it reads the list first. Invoices 1 to 7 are already there, so it starts at invoice 8. Only the unfinished invoice is checked again.

Problem 2: who decides to pay? The AI Worker only suggests, as the brief says. A person reviews the suggested list and decides the "ask" invoices. Then the payment officer sends the payments, using a payment system that blocks the AI Worker. As What stays your responsibility says, words cannot block an action, but permissions can. So even a mistaken or tricked AI Worker cannot pay.

Problem 3: what if a payment is sent twice? If the internet drops, the same payment might be sent again. So each approved invoice gets one payment ticket. The payment system pays each ticket only once and refuses a repeat.

The lesson from Brightline's run: the AI Worker does the work, but the record and the final yes live outside it.

Next, Staying safe explains why that final yes matters.