FA-18610 / Time representation / Member archive

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 05

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

Member previewVariant 5 · 3 implementations · 11 checks per implementation

Case contract

A presentation clock preserves monotonic output while exposing raw wall coordinate and rollback debt. It advances a floor by monotonic elapsed since previous sample; publish max(raw wall,floor) if continuity mode enabled, otherwise raw wall. On explicit reset, discard old floor. Output adjusted coordinate, added bias, rollback marker, debt, source mode and next checkpoint. Negative elapsed invalidates sample.

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 4	`[true, 90, 0, 0, "floor", [90, 20], true]`	`[true, 90, 0, 0, "wall", [90, 20], 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.