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

Exact minimum overlap does not count as matched · case 02

Riders sharing exactly three minutes lose the matched discount.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

In a shared ride, a rider counts as matched if they shared at least min_overlap_s seconds with another rider; a match needs at least two such riders, otherwise nobody is matched. Matched riders pay solo x (100 - discount_pct)% and unmatched riders pay solo x 95%, both floored to the cent in the rider's favor. Return id -> price.

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 fixture	Actual	Expected	Outcome
regression: overlap threshold	`{"r0": 863, "r1": 613, "r2": 1753, "r3": 2379}`	`{"r0": 863, "r1": 613, "r2": 1753, "r3": 1753}`	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.