FA-73893 / Feature flag rollout bucketing / Member archive

Flag targeting precedence: Rules are evaluated before individual targets · case 03

A QA engineer added to an individual target list still receives the variation of a broad rule.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

An off flag serves its off variation (reason OFF). Otherwise individual targets (checked by sorted variation name) win with reason TARGET, then rules in order, then the fallthrough. A rule matches only when the user has its attribute: op in = membership, startsWith = case-sensitive string prefix, lt = numeric less-than any value; negate inverts a present attribute result. Return [variation, reason, zero-based rule index or -1].

Why this case matters

Evaluation order decides whether QA allowlists, segment rules and defaults behave predictably.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
individual target beats a matching rule	`["v2", "RULE", 0]`	`["v1", "TARGET", -1]`	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.