FA-73943 / Feature flag rollout bucketing / Member archive

Segment membership precedence: Exclusion overrides explicit inclusion · case 03

A user deliberately added to a segment is dropped because an older exclusion list also names them.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

A user is in the segment if its key is in included (reason included, which beats excluded); else not if its key is in excluded; else if some rule with a non-empty clause list has every clause matching (reason rule:i). A clause [attr, values] matches only when the attribute is present and its value (or any element of a list value) is in values. Otherwise [False, none].

Why this case matters

Segments are reused across many flags, so a precedence slip changes exposure everywhere at once.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
segment sample 55	`[false, "excluded"]`	`[true, "included"]`	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.