What relationships can a generated handover dataset contain?

A handover dataset can represent a process as connected records rather than a folder of independent documents. In an insurance claim, a claim record can link to a repair assessment, a coverage review and a payment preparation task. Each branch has its own owner and completion condition.

The relationships can express more than membership in the same case. One task may block another, two tasks may proceed independently, and a final decision may require both branches to finish. A generated release can include these relationship types alongside the records they connect.

This supports cases where a transfer splits work across teams and later brings the results together. An agent must preserve the shared case context without treating completion of one branch as completion of every branch. It may also need to identify an orphan task that no longer contributes to the active case.

MirrorFirm could generate relationship tables, record histories and closure policies together. A buyer can ask for explicit links such as `blocks`, `derived_from` and `required_for_closure`, with examples showing how each affects permitted actions. The commercial material would be generated records and relationships.