FA-18019 / Time representation / Member archive

Clock offset estimator uses interval radius or discards half tick · case 04

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

Member previewVariant 4 · 3 implementations · 11 checks per implementation

Case contract

Four timestamps are ordered by message path: client send c0, server receive s1, server send s2, client receive c3. Constant offset server-minus-client is estimated by symmetric path assumption. Preserve exact half-tick fractions; report network round trip, offset, projected server now, local send/receive server equivalents, one-way path estimate and delay bounds from nonnegative path delays.

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, "2", "12", "2", [3, 7], "2", "2", "8"]`	`[true, "5", "15", "2", [3, 7], "2", "5", "11"]`	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.