Executing a merge must produce the reviewed identity change or preserve the original data after failure. Staff must be able to distinguish each durable attempt and the eventual outcome.
Execution joins contact or organization planning with participant writes, aliases and retained outcomes. Overlapping plans and participant failures require combined evidence, rather than isolated successful writes. Every sequence remains proposed until one executable selection asserts its full outcome. Existing capability assertions supply evidence for parts of the sequence.
A contact plan is ready and its approval material is current.
Steps
Submit it, process its durable work and inspect the survivor and retained outcome.
Expected
The committed values and retained originals agree with the reviewed plan.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
A ready organization plan has employee affiliations and linked contact information.
Steps
Choose its parent and retained contact details, execute the plan and inspect affected employees.
Expected
Affiliations, links and preferred addresses follow the retained organization choices.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
A run-owned plan has an injected participant failure.
Steps
Execute the plan, inspect rolled-back data and the failed attempt, remove the injected failure and request another attempt.
Expected
The failure leaves no partial identity change and each attempt remains visible with its own standing.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
A persona can read the records but lacks merge authority.
Steps
Read the records, then try to submit a ready merge plan using that persona.
Expected
Ordinary reads succeed while the unauthorized submission makes no identity change.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.
Submit repeated confirmation for one plan and execute the competing plans.
Expected
Repeated confirmation reuses its durable work and only one plan absorbs the shared contact.
Data
Use an isolated workspace, run-owned records and the permission personas described by the scenario. Failures and changed dependent records must be supplied by fixtures owned by the run.