FA-17743 / Time representation / Member archive

Day encoding erases leap metadata or adds a leap to every day · case 03

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

Member previewVariant 3 · 3 implementations · 11 checks per implementation

Case contract

A stipulated positive-leap day has label 86400 following ordinary 0..86399; a normal day does not. Return validity, atomic origin+label or None, display [hour,minute,second] (23:59:60 for extra label), final-label flag, ticks until next midnight or None, and atomic next-midnight coordinate. No real-world leap table is claimed.

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	`[false, null, [null, null, null], false, null, 186400]`	`[true, 186400, [23, 59, 60], true, 1, 186401]`	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.