How can a policy change break a handover between connected operational teams?

A warehouse coordinator marks shipment SHIP-2841 ready for collection. Its dispatch task permits unattended delivery under handling policy POL-0314. Before the carrier accepts the job, a revised policy requires a recipient signature for the shipment's product category.

The logistics agent updates the shipment record to reference the revised policy. However, the carrier booking BOOK-7612 still contains the earlier unattended-delivery instruction. A dispatch supervisor sees the updated shipment and releases it, while the receiving team acts on the stale booking.

The critical state change is not just the new policy reference. The booking must move from ready to review-required, and the receiving team must acknowledge the changed delivery obligation before dispatch proceeds. Otherwise, two connected records describe incompatible ways to complete the same work.

A generated scenario can make that mismatch visible through separate warehouse and carrier views. It teaches agent developers to treat handovers as operational commitments. Successful behaviour includes identifying the downstream instruction, updating or withdrawing it through an authorised action, and obtaining acknowledgement at the point where responsibility transfers.