Repository navigation
Configure mover exit chains and registered exit parameter bounds - #1017
Merged
seathatflowsinourveins merged 1 commit intoOct 11, 2026
Merged
Conversation
seathatflowsinourveins
marked this pull request as ready for review
October 11, 2026 19:54
seathatflowsinourveins
deleted the
foundation/mover-exit-chain-20261011
branch
October 11, 2026 21:08
This was referenced Oct 11, 2026
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.
Scope
Mover configurations can now select an exit chain such as
["X3", "X2"], soa trailing exit or first-fill time limit can fire. Simultaneous triggers use
the existing adaptive precedence: X1 calendar force, X4 stop/TP, X3 trail,
then X2 time. X2 hold and X3/X4 price ratios become bounded config fields;
legacy scalar exits and the 3600/0.85/0.85/1.50 defaults retain their behavior.
99e72aeff932fce30069092b1763736cb9e64c1b.lane:trading.and synthetic X1 activation, README, new regression tests, and their current
source/evidence hashes. RiskLimits, quote-freshness checks and exit pricing
are outside this change; the parallel freshness PR owns those paths.
SOTA sources
ebdc4d69b5c71b258485ee94aa1789b8c5646d01:GRID-2-AMENDMENT.json,SHA256
2f67ad1c0ecd6b09df3bb098e43ef769310f29c5568aebca2c25da0f0ab06738.Hold interval 900–3600 s, trail ratio 0.80–0.97; registered stop bps
1000–1500 convert to X4 ratios 0.85–0.90, and TP bps 2500–5000 to
ratios 1.25–1.50. These are candidate [C] bounds, not a selected winner.
exits.py:161-168,216-223at
1e6a49ffe8652918479e59bcb3751c0eb418e6d3.mover.py:75-79,936-954forlegacy ratios/hold/evaluation;
mover_runner.py:471-499for receipt keysand types;
safety.pyRiskLimits.frozen_json for the omission/byte-stabilityprinciple. This PR adds no RiskLimits fields or serialized limit keys.
installation and its repository native-mover harness. No new dependency,
broker adapter, model or order transport is introduced.
Evidence-class table
99e72ae; driver exit 0 verifies this expected red resultLocal commands run
Full validation passed after staging the final hashes. Source/evidence hashes cover
the changed runtime/docs and new tests; historical execution receipts are
preserved.
Decision record
The CC's rule-7 interim mover-chain direction, trading-cc's scoped direction,
and registered GRID-2 supply this change. The wider adaptive T15 policy
research remains a separate item. Array order enables rules rather than
changing protective priority. X3's high remains seeded from entry fills;
the separately proposed bid-only design is not adopted here. The synthetic
CLI retains its explicit accelerated
--hold-secondstiming override.Host evidence
No host-receipt files are changed. All new execution claims are synthetic.
Follow-ups
33d2ab61ACK, P3 verification gap: her sandbox runs 14 cases with the native case skipped and reproduces 13/14 expected main-baseline failures, so it independently verifies neither native 14/14 claim. Retain the native head and main-baseline transcripts with skip counts and dependency versions in the read packet; this gap does not establish that the reported author runs are false (tests/test_mover_exit_chain.py:243).exits.py,mover.py,mover_runner.pyandsafety.pyat native-agent-stack1e6a49ffe8652918479e59bcb3751c0eb418e6d3underextra/, and register project mirrors or document the accepted exact-object source location. Astra checked the ordinary repositories' exact objects and found the citations supported; GRID-2 is captured and hash-verified, while those four independent captures are missing (body source citations;mover.py:82).mover_runner.py:679,684,738,804,896). If independent reconstruction is required for those artifacts, add a separately scoped policy snapshot and startup/crash regression; no defect was demonstrated in this PR's completed-run projection.Checklist