FA-74277 / Feature flag rollout bucketing / Member archive

Traffic then variant allocation: Arm weights are scaled by traffic · case 02

At partial traffic most allocated users fall through to the last arm.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Stage 1: t = crc32(salt + ":traffic:" + user) % 100; users with t >= traffic (1..100) are not in the experiment. Stage 2 uses an independent v = crc32(salt + ":variant:" + user) % 100 and walks weights ([arm, percent of allocated users], summing to 100) cumulatively, half-open. Return [in_experiment, arm or None].

Why this case matters

Separating traffic allocation from the variant split keeps arms balanced when traffic changes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
allocation sample 6	`[true, "c"]`	`[true, "b"]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.