FA-17882 / Time representation / Member archive

Fractional timestamp digits are aligned as integers instead of decimal places · case 02

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

Member previewVariant 2 · 3 implementations · 20 checks per implementation

Case contract

Parse exact ASCII signed decimal epoch seconds: optional one leading minus, nonempty whole digits, optional dot plus one to three fractional digits. Reject whitespace, plus, comma, exponent, empty fraction, non-ASCII digits and excess precision. Return validity, exact signed milliseconds or None, and negative-zero lexical marker. No floating point is used.

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	`[true, 1002, false]`	`[true, 1200, 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.