FAILURE MAP
← Case archive

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

Highest multiplier overrides zone priority · case 02

An event overlay with priority 2 loses to a base zone with a higher multiplier.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Surge zones are rectangles, half-open [x0, x1) x [y0, y1). The multiplier comes from the pickup point only. Among zones containing it choose highest priority, then highest multiplier, then lowest id. No containing zone gives [None, 10] (1.0x in tenths). Return [zone id, multiplier].

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: priority before multiplier[18, 20][1, 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.

Sign in to the archive ↗