How do you test an agent when the obligation changes while it is working?

An insurance accounts officer reads premium invoice INV-3094 and prepares a reminder because the payment is overdue. Before dispatch, event EVT-0826 posts a matching payment and changes the invoice status to settled. The draft still contains a request for payment.

The environment rejects dispatch because the action refers to an earlier record version. The agent receives a conflict result, refreshes the invoice and discovers the settlement. It should cancel the draft or record that the planned contact is no longer required, according to the available actions.

An agent that blindly retries with the latest version would still fail the business task. Version freshness is necessary, but the refreshed state must change the decision. The episode should therefore inspect both tool handling and the resulting communication behaviour.

A generated evaluation case can place the payment event at a controlled point between inspection and dispatch. The consequence is observable: no incorrect payment demand is sent, and the case records why planned contact stopped. This tests recovery from concurrent change rather than performance on a static snapshot.