FA-18554 / Time representation / Member archive

Deadline transfer uses opposite guarantee or midpoint estimate · case 04

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

Member previewVariant 4 · 3 implementations · 11 checks per implementation

Case contract

A deadline in source clock D maps to target clock with uncertain target-minus-source offset [lo,hi]. Use earliest target deadline for no-late policy, latest for no-early. Account for known transport time in target units and clamp remaining budget at zero. Relative waits are capped by platform maximum and flag rearming. Return target bounds, chosen deadline, wait, rearm and expired status.

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	`[[22, 25], 25, 13, false, false, 25, 3]`	`[[22, 25], 22, 10, false, false, 22, 3]`	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.