How could generated records represent a handover that splits into separate branches?

A returns supervisor opens `RET-3064` after a supplier accepts a damaged stock claim. The acceptance covers a credit, but the goods must remain quarantined until disposal instructions arrive. The supervisor transfers the case to finance and inventory control.

Finance records expected credit `CRD-1182`. Inventory control creates hold `HOLD-0729`. When the credit arrives, the finance branch changes to settled. The stock branch remains blocked because no disposal instruction has been issued. Closing the parent return at this point would remove the unresolved hold from the supervisor's active review.

A generated environment could contain the supplier acceptance, credit ledger entry, stock hold, disposal policy and parent-child links. It could also contain a closure rule requiring both branches to meet their own completion conditions. The agent's available actions would update each branch independently.

This teaches evaluators to test fan-out and recombination. A shared origin does not imply a shared finishing condition. The task can expose agents that treat the most visible successful outcome as proof that the entire handover is complete.