FA-66660 / Airline fare rule evaluation / Member archive

Travel on the last valid day treated as expired · case 05

Starting travel exactly one year after issue is refused.

Member previewVariant 5 · 3 implementations · 11 checks per implementation

Case contract

Input {'issue','first_travel' (ISO or None)}. One calendar year = same month/day next year (29 Feb -> 28 Feb). Unused -> ['UNUSED', issue+1y]. First travel later than issue+1y -> ['EXPIRED_UNUSED', issue+1y] (travel on that date is still valid). Otherwise ['TRAVEL', first travel+1y].

Why this case matters

Normal ticket validity runs one year from issue until travel commences, then one year from first travel, with calendar-year and leap-day rules.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
travel exactly one year after issue	`["EXPIRED_UNUSED", "2028-05-15"]`	`["TRAVEL", "2029-05-15"]`	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.