FA-74339 / Feature flag rollout bucketing / Member archive

Per-context evaluation memo: Memo depends on attribute insertion order · case 04

Identical contexts built in different orders miss the cache and double evaluation counts.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

calls are [flag, context dict of string attributes, flag version]. The toy evaluation is (sum of code points of flag + key + country) + version) % 3. Results are memoised by (flag, context contents independent of attribute order, version). Return [value, hit|miss] per call.

Why this case matters

Evaluation caches in SDKs must key on every input that can change the result.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
call sequence sample 7	`[[2, "miss"], [1, "miss"], [1, "miss"], [0, "miss"], [1, "miss"], [1, "miss"]]`	`[[2, "miss"], [1, "miss"], [1, "hit"], [0, "miss"], [1, "miss"], [1, "miss"]]`	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.