What could a generated pack contain when a household arrangement changes?
A household separation can produce linked insurance records whose ownership, correspondence and insured interests must be separated without losing their prior relationships.
An insurance customer tells a service adviser that a shared household has separated. Under CASE-0412, the customer requests separate correspondence and asks which items remain associated with POL-2187. The policy contains insured interests held individually and jointly, while the contact record uses a shared mailing preference.
The adviser separates correspondence instructions for the requesting customer and refers jointly held items to a policy specialist. The specialist records the required agreement before changing those interests. The resulting records represent separate contact preferences without treating the customer's request as permission to transfer every insured item.
A generated pack can contain the incoming message, household membership links, policy parties, item ownership records, correspondence preferences and a task-specific consent rule. It can also contain the prior relationship state and the proposed new state, connected by change reasons rather than overwritten history.
The consequence of an incorrect update is concrete: a document can reach the wrong recipient, or an item can be assigned to a party without the required agreement. This scenario teaches a model to restructure relationships selectively. It also gives labs material for distinguishing a change to a group relationship from changes to the rights attached to individual records.
Train relationship restructuring with records that preserve history while representing the customer's new arrangement.
- Audience:
- Model labs
- Content type:
- Scenario
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- What evidence artefacts should accompany a generated change request?
- Can generated environment state include disagreement between connected systems?
- Which relationships can a generated dataset contain around a customer change?
- How can generated change material be packaged for an agent harness?
- How can a task pack represent a change governed by different policy versions?
- What policies and authority relationships could a generated environment contain?