FA-17972 / Time representation / Member archive

Definite timestamp ordering ignores measurement width · case 02

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

Member previewVariant 2 · 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 1	`[[15, 20], true, true, false, true, [10, 35]]`	`[[15, 20], false, true, false, true, [10, 35]]`	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.