Fix the two-way exchange scope
Synthetic confirmed swap SW2 moves DEV-A from S8 to S9 and DEV-B from S9 to S8. Local active-assignment rule gives each device one custodian and these staff one of these devices each. Both physical acknowledgements already exist; the task updates the two-row custody record together, not one row copied over the other.
| Device | Old custodian | New custodian |
|---|---|---|
| DEV-A | S8 | S9 |
| DEV-B | S9 | S8 |
Prepare the complete replacement pair
- Read both SW2 acknowledgements
- Prepare both new rows from old pair
- Check unique device and staff assignments
- Record one completed swap with old/new pair
One missing acknowledgement leaves the swap unrecorded as complete; do not record a one-sided final pair.
What is the final pair and active assignment count?
Show the worked answer
DEV-A→S9 and DEV-B→S8, two active associations. Old associations are historical; there are not four active loans.
Check the pair before recording completion
| Case | Action or result | Evidence boundary |
|---|---|---|
| UpdateDEV-A only as final | Reject incomplete swap | S9 would have both devices |
| Replace complete pair underSW2 | Accept | Two unique new custodians |
The swap record retains both movement acknowledgements and both association revisions. Subsequent device queries use the active pair, not all history rows.