Read the verified replacement mapping
Synthetic variant A currently uses file F-A1. Verified replacement decision maps new file F-A2 to the same logical variant A and retires F-A1 from the active pack. Exposed unit U32 remains assigned A. File F-B belongs to variant B. Local administration changes A’s file reference, not U32’s experiment bucket; all replacement content evidence is supplied, not inherited from old approval.
| Identity level | Before | After |
|---|---|---|
| Variant A file | F-A1 | F-A2 |
| U32 bucket | A | A |
| Variant B file | F-B | F-B |
Bind the new file to the same variant
- Match supplied F-A2 replacement to A
- Change A’s active file reference
- Retain U32/A and B/F-B
- Remove F-A1 from active pack with history retained
Do not move U32 to B merely to avoid the retired F-A1 file.
Which variant/file serves U32 after replacement, and how many bucket changes result?
Show the worked answer
Variant A with F-A2; zero bucket changes. Retiring a file revision does not retire the supplied logical variant or its frozen episode assignment.
Retain the exposed unit’s assignment
| Case | Decision or result | Reason |
|---|---|---|
| Swap U32 to B/F-B | Reject variant crossover | Only file replacement authorised |
| A now maps F-A2, U32 stays A | Accept | Three identity levels preserved |
Record the replacement decision, old/new file references and retained episode key together. Inspect the delivered F-A2 against its own supplied content evidence.