FA-18360 / Time representation / Member archive

Epoch range check mishandles asymmetric signed bounds · case 05

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

Member previewVariant 5 · 3 implementations · 11 checks per implementation

Case contract

A clock uses signed 16-bit seconds relative to configurable epoch E and fractional nanoseconds. Source absolute total nanoseconds is exact integer. Convert to canonical seconds/remainder relative to E, mark representability, and serialize biased unsigned seconds word only if in range. Provide saturation coordinate, loss amount, earliest/latest representable total and exact reconstruction.

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 3	`[null, 0, false, -32758000000000, 0, [-32758000000000, 32777999999999], null]`	`[0, 0, true, -32758000000000, 0, [-32758000000000, 32777999999999], -32758000000000]`	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.