FA-17955 / Time representation / Member archive

Precision comparison ignores clock domain or hardcodes UTC · case 05

The decoded time state disagrees with the explicit regression oracle for compatible.

Member previewVariant 5 · 3 implementations · 11 checks per implementation

Case contract

A timestamp rounded down to resolution q represents half-open [stamp,stamp+q). Preserve domain tag; q positive. Comparing two buckets yields exact intersection and possible/definite-before relations, equality of represented sets and union envelope. Query membership is half-open. This model handles precision buckets, not point timestamps.

Why this case matters

Clock transfer and timestamp consumers require preserved coordinate, phase, validity and elapsed-time semantics.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 6	`[[2, 5], false, true, false, true, [0, 10]]`	`[null, false, false, false, true, null]`	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.