A single order may change the price it rests at — and only if a limit order of its own is still on the books; a trigger price cannot be changed at all. Work fed out in slices may change how many parts and the gap between them, except where the parts are weighted, which may change only the gap. Work at several prices may change those prices, their weights, or both. A part-shown order may change its shown amount, its price, or both. Either way a change naming neither is refused. Protection has three prices that can change.
What is refused on the way in
A change naming a request Praxis does not know is refused, and so is one naming a request belonging to another account.
A change that would raise what a buy commits above what the original committed is refused. Prices may move and parts be re-cut, but not so as to ask the account for more than it agreed to. A sell has no such limit, committing coin it already holds.
Every change passes those tests before being queued, protection included.
Afterwards
A change reaching a request that has already finished normally does nothing further. A finished opening request whose protection is still live is the exception: it can still be named, to change that protection.
Two changes arriving together queue for processing one at a time. Where the first parks awaiting fills, the second does nothing when its turn comes.
Related
Source evidence
---
row: P3-13
baseline: 49aa659
created: 2026-09-30 05:58 UTC
modified: 2026-10-12 01:12 UTC
evidence:
- claim: "Each way of working has one kind of change that fits it"
source: "`modify_params.py` 31-39, matched at `validate_trade_modify.py` 193-198"
- claim: "A single order may change the price it rests at, and a trigger price is refused"
source: "`validate_trade_modify.py` 200-208"
- claim: "Only a limit order the account still holds a record of is changed at all"
source: "`execution_manager.py` 8680-8685"
- claim: "Sliced work may change its count and its gap"
source: "`interval_slice_modify.py` 31-32"
- claim: "Weighted work may change only the gap, its weights refused and its count kept"
source: "refused at `validate_trade_modify.py` 210-218, kept at `execution_manager.py` 10189-10199"
- claim: "Work at several prices may change its prices, its weights, or both, and at least one of them"
source: "`ladder_dca_modify.py` 36-37, at least one required at 43-45"
- claim: "A part-shown order may change its shown amount, its price, or both, and at least one of them"
source: "`iceberg_modify.py` 29-30, at least one required at 36-40"
- claim: "Protection has three prices that can change"
source: "`execution_manager.py` 9871-9907"
- claim: "A change naming an unknown request is refused"
source: "`validate_trade_modify.py` 180-182"
- claim: "A change naming another account's request is refused"
source: "`validate_trade_modify.py` 184-189"
- claim: "A change raising what a buy commits above the original is refused"
source: "`validate_trade_modify.py` 220-226"
- claim: "Every change passes those before being queued, protection included"
source: "`execution_manager.py` 3060-3065"
- claim: "A change to a request already finished normally does nothing further"
source: "`execution_manager.py` 8622-8624"
- claim: "A finished opening request whose protection is still live can still be named to change it"
source: "`validate_trade_modify.py` 171-175, routed ahead of the finished test at `execution_manager.py` 8616-8620"
- claim: "A change parked awaiting fills is not replaced by a second"
source: "`execution_manager.py` 8631-8636"
- claim: "Changes are processed one at a time by the account's own worker"
source: "`execution_manager.py` 3910-3939, queued without a check at 3060-3074"
---