Read the variant tuple
Synthetic assets V1 EN square O5 and V2 zh-HK square O5 both arrive as “launch-final”. V3 EN wide O5 is separate. Local manifest uses immutable variant IDs plus locale/format/offer fields; files get distinct delivery keys K1/K2/K3. It does not rename V2 into V1 or infer translation equivalence.
| Variant | Locale/format | Delivery key |
|---|---|---|
| V1 | EN/square | K1 |
| V2 | zh-HK/square | K2 |
| V3 | EN/wide | K3 |
Assign distinct delivery keys
- Inspect full variant tuples
- Keep V1/V2/V3 identities
- Assign unique delivery keys
- Update placement references by variant
A shared filename is not enough evidence to overwrite or merge variants.
How many variants and distinct delivery keys are required?
Show the worked answer
Three variants and three keys. The V1/V2 filename collision is removed without collapsing the locale distinction.
Verify every reference resolves once
| Case | Decision or result | Reason |
|---|---|---|
| Overwrite V2 with V1 | Reject | Loses Chinese variant |
| K1/K2 with distinct tuples | Accept | References unambiguous |
Test the destination manifest using variant IDs, not a “final” filename search. Content review remains attached to its actual variant.