FAILURE MAP
← Case archive

FA-85615 / Ride-hailing fare and surge pricing / Member archive

Quote honored at the exact expiry second · case 05

A request exactly five minutes after the quote still uses the locked surge.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

A fare quote locks its surge for 300 seconds: requests with 0 <= elapsed < 300 seconds are locked (a request timestamped before the quote, from clock skew, is not). A locked request uses the lower of the quoted and current surge; otherwise the current surge. Price = core x surge / 10, half up. Return [price, locked|requoted].

Why this case matters

Ride-hailing prices are computed per trip at scale; ordering, unit and boundary slips become systematic over- or under-charging.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
regression: lock expiry instant[1499, "locked"][1998, "requoted"]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.

Sign in to the archive ↗