The plain single order
Up to three prices, each of which may be left unset: the price to rest at, the price that triggers, and the price a triggered leg rests at. Which are needed turns on the kind of order.
A price that is set must be above nought. That is a comparison alone, so an endless price passes, as does a whole or floating-point number; a not-a-number breaks on the comparison itself.
A fixed pace
Two whole numbers, used as a count of parts and a gap in seconds. The count must be at least two; the gap must be above nought.
Both refuse true and false outright, before either bound is weighed.
A weighted pace
A gap in seconds, tested the same way, and a tuple of weights.
There must be at least two weights, each a finite decimal above nought, adding to exactly one with no tolerance. Rounding as they are added is the slack: a pair whose true total sits a shade either side of one can still add to one, and pass.
No count of parts is carried here. It is taken as the count of weights.
A protective pair
Each leg of a protective pair takes exactly one of an outright price or a distance from the entry; both, or neither, is refused as the settings are built. Every figure set, the price a stopped leg rests at included, must be a finite decimal above nought.
Related
Source evidence
---
row: P4-08
baseline: 49aa659
created: 2026-10-03 14:12 UTC
modified: 2026-11-09 14:05 UTC
evidence:
- claim: "Seven ways of working share six kinds of settings between them"
source: "`execution_params.py` 30-38"
- claim: "Feeding work out at a fixed pace and buying at a fixed pace take the same kind, and no other pair does"
source: "`execution_params.py` 30-38"
- claim: "A command must carry the kind its way of working registers"
source: "`praxis/core/domain/trade_command.py` 118-124"
- claim: "The plain single order takes up to three prices, each of which may be left unset"
source: "`single_shot_params.py` 30-32"
- claim: "Which are needed turns on the kind of order"
source: "`validate_trade_command.py` 221-246"
- claim: "A price that is set must be above nought, tested by comparison alone"
source: "`single_shot_params.py` 38-42"
- claim: "The fixed-pace kind takes two whole numbers, used as a count of parts and a gap in seconds"
source: "`interval_slice_params.py` 30-31, used at `execution_manager.py` 5926"
- claim: "The count must be at least two"
source: "`interval_slice_params.py` 37-43, the least set at 16"
- claim: "The gap must be above nought"
source: "`interval_slice_params.py` 45-51"
- claim: "Both refuse true and false outright, before either bound is weighed"
source: "`interval_slice_params.py` 37-43 and 45-51, the bool test standing first in each"
- claim: "The weighted kind takes a gap in seconds, tested the same way, and a tuple of weights"
source: "`scheduled_vwap_params.py` 35-36 and 42-48"
- claim: "There must be at least two weights, arriving as a tuple"
source: "`scheduled_vwap_params.py` 50-52, the least set at 20"
- claim: "Each weight must be a finite decimal above nought"
source: "`scheduled_vwap_params.py` 54-60"
- claim: "Adding the weights must give exactly one, with no tolerance in the comparison"
source: "`scheduled_vwap_params.py` 62-64, the one at 19"
- claim: "Rounding while they are added can let a total slightly off one pass"
source: "`scheduled_vwap_params.py` 62"
- claim: "The count of parts for the weighted kind is taken as the count of weights"
source: "`execution_manager.py` 467-471, then 473-474, the parts planned at `plan_weighted_slices.py` 58-62 by the road taken at `execution_manager.py` 489, then 490, against 492, and counted at 5767"
- claim: "Each leg of a protective pair takes exactly one of an outright price or a distance, every figure being a finite decimal above nought"
source: "`praxis/core/domain/bracket_params.py` 51-57, all five figures weighed at 59-71"
---