FA-74195 / Feature flag rollout bucketing / Member archive

Exposure event deduplication: Events are processed in arrival order · case 05

Late-arriving older events are emitted after newer ones and suppress the wrong exposures.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

events are [t, user, flag, variant] processed in timestamp order (stable for ties). An exposure is emitted unless the same (user, flag, variant) was emitted less than window seconds earlier; suppressed events do not move the window. Return emitted indices in processing order.

Why this case matters

Exposure logs define who entered an experiment; duplicates and gaps both bias analysis.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
events are processed in time order	`[0, 2]`	`[1, 2, 0]`	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.