FA-18065 / Time representation / Member archive

Hybrid logical carry uses the largest label rather than counter capacity · case 05

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

Member previewVariant 5 · 3 implementations · 12 checks per implementation

Case contract

A bounded hybrid logical timestamp has physical integer p and logical integer l, cap 255. On receive, p=max(local p,remote p,wall). Increment max logical when both timestamps share p, increment owning side when only one shares p, otherwise reset logical to zero. Carry logical overflow into physical. Return canonical pair, physical source mask, ordering versus inputs and wall-advance flag.

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 11	`[[11, 255], 3, true, true, true]`	`[[10, 255], 3, true, true, 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.