Feedback is diluted
Narrow gains disappear in full-data replay, while broad edits often violate coupled objective guardrails.
HKUST (Guangzhou) · DiDi Chuxing
01
Ride-hailing dispatch engines must adapt continually to changing demand, supply, and driver behavior while protecting several coupled business objectives. Production improvement, however, still relies heavily on experts to identify a scenario, propose a policy change, validate it by offline replay, and advance it to an online A/B test.
We formulate the task as constrained multi-objective dispatch engine evolution and propose DispatchEvolve. Trace-Grounded Local Policy Evolution constructs scenario-specific opportunities from decision traces and replay outcomes, filters them with an opportunity critic, and evolves only the relevant policies under local guardrails. Pareto-Guided Global Engine Integration models relations among the resulting candidates, evaluates their combinations as complete engines, and retains globally feasible, non-dominated improvements in a cross-round archive.
On frozen test logs from four cities, DispatchEvolve is the only evaluated method that improves all six objectives over the incumbent in every city. Only 25 of 147 complete-engine compositions improve all six objectives while satisfying the broadcast-rate constraint, confirming that local gains are not reliably additive.
Why
Direct program evolution assumes that nearby edits provide direction, the target is already known, and local improvements compose. Industrial dispatch violates all three assumptions.
Narrow gains disappear in full-data replay, while broad edits often violate coupled objective guardrails.
A weak scenario may be exogenous; actionable gaps require trace evidence and policy attribution.
Policies can reinforce, cancel, duplicate, or conflict once assembled into a complete engine.
02
DispatchEvolve separates the problem into two connected search spaces: focused local evolution where the signal is visible, then full-engine integration where coupled constraints are measurable.
Evidence
Output · locally validated policy candidates
Output · globally feasible Pareto archive
A/B-ready
engine
The online-uplift assessment ranks only engines already proven feasible by offline replay. It never changes the objective vector or the Pareto relation.
03
The only evaluated method to improve all six objectives in every offline city.
Search trajectory
City A ablation · Avg. Δ
Without explicit candidate relations, independently evolved policies cannot be reliably integrated into a feasible engine.
Opportunity actionability
Across 560 local searches, a larger scene performance gap does not predict whether evolution will succeed. The DPO-tuned Qwen3-8B critic reaches 63.2% decision accuracy, compared with 42.7% for the base model.
17.0%
25 / 147
Local candidates can overlap in scenes, policies, and metrics. DispatchEvolve therefore never sums their isolated gains: each composition is installed into a runnable engine and evaluated against all six objectives plus the broadcast-rate constraint.
Richer Pareto context accompanies more feasible proposals, but it never replaces complete-engine replay.
04
A trace-localized ETA filter edit improves its target scene but carries an ETA trade-off. Global integration combines it with 15 complementary candidates and absorbs that local cost.
Policy-trace case study
Local candidate · paired scene replay
Integrated engine · full replay
All values are direction-aligned: positive is favorable after accounting for whether higher or lower is preferred.
05
Four production A/B tests connect offline evolution to live marketplaces.
| City | CR ↑ | GMV ↑ | AR ↑ | DCAA ↓ | ETA ↓ |
|---|---|---|---|---|---|
| City A | +0.72%* | +1.32%*** | +0.49% | −3.09%** | +0.82%*** |
| City B | +0.58% | +0.18% | +0.51% | +1.04% | −0.71% |
| City E | +1.07%** | +0.94%** | +0.97%*** | +1.98% | −0.03% |
| City F | +0.46% | +0.48% | +0.37% | −0.82% | +0.32% |
Six nominally significant improvements and one nominally significant ETA degradation. City-level monitoring remains essential after deployment.
No LLM inference, model loading, or additional service is required in the online dispatch path.