FA-74162 / Feature flag rollout bucketing / Member archive

Network allowlist clause: Octets above 255 are accepted · case 02

An entry such as 1.0.0.256/8 is parsed into an unrelated network instead of being skipped.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

ip is dotted-quad IPv4 with octets 0..255 (else return None). Each cidr is "a.b.c.d/n" with 0 <= n <= 32, or a bare address meaning /32; malformed entries are skipped. An entry matches when the top n bits of ip and of its address agree (host bits of the entry are ignored). Return [True, index of first match] or [False, -1].

Why this case matters

Office and VPN allowlists gate internal features by source network.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
octet 256 in an entry is malformed	`[true, 0]`	`[false, -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.