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

One-way adjacency entries ignored · case 02

Zone B smooths from A but A never smooths from B.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Smooth zone multipliers (tenths): each zone publishes the max of its own raw multiplier and each neighbor's raw multiplier minus 5, clamped to [10, 30]. Adjacency is symmetric even when listed once; neighbors without a raw multiplier are ignored; all reads use raw values, never already-smoothed ones. Return zone -> published 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 fixture	Actual	Expected	Outcome
regression: symmetric adjacency	`{"A": 10, "B": 15, "C": 20}`	`{"A": 15, "B": 15, "C": 20}`	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.