Repository navigation
feat(dispatch): implement Phase 17 multi-order admission and execution - #22
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Allow a new order to be inserted into an occupied rider's remaining plan while preserving ownership, custody and active travel/wait/service. Dispatch exhaustively evaluates every eligible rider and order-preserving pickup/dropoff placement using whole-plan timing, prefix capacity and hard service protections, then minimizes signed incremental road-travel seconds, road distance and canonical identity.
Validation
cargo fmt --all -- --checkcargo +1.99.0 clippy --workspace --all-targets --all-features --locked -- -D warningscargo +1.99.0 test --workspace --all-features --locked: 159 tests pass.scripts/collect_multi_order_benchmark.py: all 11 scenarios replay byte-for-byte across 11 measured runs each; coverage/work/publication invariants verified.git diff --checkpass.The successful pooling fixture assigns B during A's active execution, delivers both orders and records one 45.008-second busy interval. Benchmarks record hardware, compiler/build, dataset hashes, raw timing samples, median/p95/p99 and deterministic work; memory is explicitly unmeasured. These small synthetic datasets make no scalability claim.
Completion and scope
Phase 17 completion report records PASS for all 24 gates, scenario results, benchmark configuration/results and limitations. Normative audit preserves the confirmed Phase 18 contracts.
There are no queued editable future stops; active actions retain independent execution identities. Any later introduction of queued editable work must add plan-generation binding. Exhaustive insertion has a deterministic placement budget, while baseline input/health evaluation occurs before that budget.
Phase 18 implementation remains deferred until explicit user confirmation.