FA-309 / Time representation / Member archive

Sorting local timestamp text reverses the order of absolute instants · case 04

An event with a later wall-clock reading is placed after an event that actually occurred later in UTC.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Given [identifier, ISO timestamp] records with explicit numeric offsets, return identifiers in increasing absolute-time order. Keep input order for ties. This models explicit fixed offsets only, not named-zone DST resolution.

Why this case matters

Correlating logs from different offsets requires a common time basis. Text sorting is safe only under a much narrower normalized-format contract.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
positive offset reverses wall-clock order	`["utc", "east"]`	`["east", "utc"]`	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.