Which exception families should a generated handover pack cover?

Ask for exception families that change the next valid action, with enough generated context to explain the recovery path.

- A destination queue has been retired but remains in an old template. - An attachment reference resolves to an inaccessible document. - A delegate receives work outside their delegated authority. - A receiving team requests evidence already held elsewhere. - A source request is cancelled while specialist work continues. - An urgent transfer arrives during a declared processing freeze.

Each family should include the trigger, the records affected and the permissible response. A missing attachment case is weak if the only possible behaviour is to stop. It becomes more useful when the agent can distinguish a broken reference from a permission problem and choose an appropriate recovery action.

The pack can also vary surface wording within each family so that agents cannot solve the task by memorising one phrase. Keep the underlying rule stable enough for the expected behaviour to remain explainable.

For developers, this creates a practical curriculum: recognise the exception, retrieve the missing context, choose a valid recovery path and leave a record of what prevented normal processing.