FA-17524 / Time representation / Member archive

Clock interval width is confused with radius · case 04

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

Member previewVariant 4 · 3 implementations · 11 checks per implementation

Case contract

Project a center with asymmetric early/late error through signed elapsed ticks. Error growth uses elapsed magnitude and independent parts-per-thousand bounds rounded outward. Return projected [low,high], full width, zero containment, earliest/latest signed query duration and strict certainty of preceding query.

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	`[[8, 15], 23, false, [5, 12], true]`	`[[8, 15], 7, false, [5, 12], true]`	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.