Repository navigation
Clarify submission and routed order planning flow - #46
Merged
Richard-LZ-Zhang merged 1 commit intoOct 27, 2026
Merged
Conversation
Richard-LZ-Zhang
merged commit Oct 27, 2026
8e0c517
into
codex/order-lifecycle-storage
5 checks passed
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.
Submission and routed replanning were difficult to follow because orchestration, retry reservation, venue dispatch and persistence were interleaved. Extract named submission helpers and document routing policies, callbacks and leg cleanup; rename
budgetandmay_moveto describe their actual purpose.Preserves submission locks, dispatch locks, exception handling and existing allocation behavior. Adapted onto
7084154ofcodex/order-lifecycle-storage, retaining its cross-venue bucket authorization and retry flow; the older nominal-venue helper extraction was superseded by that upstream change. This PR targets the experimental branch, not publicmain.Validation: 506 offline tests passed across engine submission, managed orders, routing/recovery, storage, duplicate risk, stops and core routing. Reviewed the extraction and renamed consumers for regressions. No live execution or release.
Known cancellation correctness concerns remain tracked in PRE-10; design and documentation follow-ups remain in PRE-11. Neither issue is closed by this readability change.