Skip to content
Astera Technology

Preserve an exposed unit’s variant after an allocation change

Use recorded exposure for existing units and the new map only for unexposed entrants.

Read exposure history and new map

Synthetic revision R1 assigned scores 0–49 to A,50–99 to B. R2 changes A to 0–24 and B to 25–99. Local experiment keeps a unit’s first recorded exposed variant for its current episode. U1 score 30 exposed A, U2 score 70 exposed B, U3 score 30 never exposed. No random assignment or real traffic claim is made.

Frozen exposure/new entrant mapping
UnitHistoryNext recorded assignment
U1 score 30A under R1A retained
U2 score 70B under R1B retained
U3 score 30No exposureB under R2
Download editable CSV ↓

Separate existing units from new entrants

  1. Look up episode exposure by unit
  2. Retain U1/A and U2/B
  3. Use R2 only for U3
  4. Flag proposed U1 crossover

A deliberate new episode needs its own episode identity and policy; do not silently reset an existing one.

How many existing units would change incorrectly if R2 were reapplied blindly?

Show the worked answer

One, U1, from A to B. U2 stays B; U3 legitimately enters B because it has no exposure history.

Reject unintended variant crossover

Filled campaign-operation checks
CaseDecision or resultReason
Recompute U1 from score 30 onlyReject crossoverRecorded first exposure A
Apply R2 to unexposed U3Allowed locallyNew entrant
Download editable CSV ↓

Record the retained assignment source, not merely the latest map revision. Allocation edits do not rewrite earlier exposure events.

Related resources