FA-66727 / Airline fare rule evaluation / Member archive

Unrecognised suffix tokens silently dropped · case 02

A corrupted basis such as MH14ZZ decodes as valid with no flags.

Member previewVariant 2 · 3 implementations · 12 checks per implementation

Case contract

Input: a fare basis string. Grammar: RBD letter A-Z (ASCII uppercase, else 'ERR_BASIS'), optional season H|L, optional day code W (WEEKEND) | X (WEEKDAY), optional advance purchase digits of any length (default 0), then two-letter tokens from CH, IN, NR (otherwise or odd length -> 'ERR_TOKEN'). Return {'rbd','season','days','ap','flags'}.

Why this case matters

Fare basis codes pack booking class, season, day-of-week application, advance purchase and passenger/penalty indicators into a positional code.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
unknown suffix token	`{"ap": 14, "days": "ANY", "flags": [], "rbd": "M", "season": "H"}`	`"ERR_TOKEN"`	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.