Repository navigation
feat: add a reproducible public-market matching case - #14
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
1 participant
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.
TradeForge's published execution evidence was synthetic. This adds a 40-second public DOGEUSDT depth capture and an offline, narrowly scoped aggressive-matching case. It validates snapshot bridging, continuous depth update IDs, complete packet states, known top-ten coverage, timestamps and exact integer price/base-asset units. No orders are sent.
The same quantity/window is compared across immediate matching and ten time slices, three latency scenarios and three fee scenarios, retaining all 18 cells. Source packets, capture hash, full results and explicit limitations are saved. In this episode the 0/1/10 ms scenarios have identical prices; this is retained, with observed book age and the 100 ms feed limit. The case does not claim measured order latency/account fees, exact passive queues, full OMS validation or endogenous market impact.
Validation: Python suite passes after respecting the existing application-layer boundary and function-size rule; Ruff formatting/lint and strict mypy pass. Added offline reproducibility, sequence-gap rejection, fractional-unit rejection and notional/cost reconciliation checks. CI replays the frozen episode without network access.