FA-74305 / Feature flag rollout bucketing / Member archive

Timestamp targeting clause: Offset timestamps are read as UTC · case 05

A clause user value of 23:13:20+01:00 is treated as 23:13:20 UTC, an hour late.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Values are epoch milliseconds (int or float) or UTC strings exactly "YYYY-MM-DDTHH:MM:SSZ" converted to milliseconds; booleans, other strings and invalid dates are unusable and make the clause false. op before means user < clause, after means user > clause (strict); other ops are false.

Why this case matters

Date clauses schedule launches and trials; unit and timezone slips shift them by days or years.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
explicit UTC offset spelling is unusable	`true`	`false`	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.