Work that never started
Work meant to be fed out in slices, or placed at several price levels is measured when the worker takes it off the queue; past the time by then, it ends there, reported expired with nothing sent.
An opening order with protection attached skips this check, and so does one showing the market only part of its amount.
Work that was sent
Only work sent in one go is measured after its send; a linked pair counts. Even then the clock is read only where the status just worked out is waiting or part filled, though every status is reported by the same call.
The moment used is taken when the send returned, or when a chased send was adopted. Past the time by then, the request is settled as expired and a cancel is attempted.
Short of the time at that moment, the order is reported as it stands and never measured again: a resting order whose deadline arrives an hour later is untouched.
A second clock
Work being fed out, and a ladder, get a fresh clock when they start. The way in refuses only a gap at or below nought, so one comparing neither way is taken and then breaks the pass that turns it into a moment, leaving the work as it was. Past that clock a run only begins winding up: its children are asked to cancel, and it stays on the books until they settle. Work already waiting for its orders to finish, or being changed, is skipped entirely.
Related
Source evidence
---
row: P2-23
baseline: 49aa659
created: 2026-09-24 20:16 UTC
modified: 2026-11-09 13:36 UTC
evidence:
- claim: "A deadline counts as passed where the moment given stands at or past it"
source: "`execution_manager.py` 2939"
- claim: "The clock runs from the time supplied on the command, not from the accept written later"
source: "`execution_manager.py` 2925 reading the time stored at 3476, the accept taking its own clock at 3517"
- claim: "Work fed out or laddered, dequeued past that time, is ended before it starts"
source: "either `execution_manager.py` 3995-3996 or 4004-4005, into 4123-4129"
- claim: "Only work sent in one go is measured after its send, a linked pair included"
source: "`execution_manager.py` 4008-4009, the pair cancelled by its own call at 4419-4424"
- claim: "It is measured only where the status just worked out is pending or partial"
source: "`execution_manager.py` 4411-4414"
- claim: "A quote-sized order is called filled on the venue saying so with something filled; a quantity-sized one on its fills covering the amount"
source: "either `execution_manager.py` 4395-4396 or 4403-4404"
- claim: "Every status, a full fill included, is reported by the same call at the end"
source: "`execution_manager.py` 4446-4448"
- claim: "The moment used is taken when the send returned, or when asking the venue confirmed it had taken the order"
source: "stored at either `execution_manager.py` 4281 or 4291, compared at 4414"
- claim: "A bracket and a hidden-size order are measured against neither clock"
source: "dispatched by either `execution_manager.py` 4000 or 4002, the one sending at 4521 and the other returning at 5396, neither reading a clock"
- claim: "A run or a ladder that starts gets a fresh clock, opened from the moment recorded at its start, where the gap it was given compares above nought"
source: "either `execution_manager.py` 5784-5787 from the time taken at 5760, or 6128-6131 from 6107"
- claim: "The gap is refused on the way in by comparison alone, so one comparing neither way is taken and breaks the pass that measures it"
source: "`praxis/core/domain/trade_command.py` 106-108, measured at either `execution_manager.py` 3995 or 4004 by way of 2925, logged at 4012"
- claim: "The same pass begins winding either of them up against that clock"
source: "`execution_manager.py` 5814, then 5816-5824, which skips one already draining or mid-change at 5817-5821"
- claim: "Winding up cancels children and leaves the run on the books until they settle"
source: "`execution_manager.py` 8375-8383, held open at 6355-6356 while a child remains"
- claim: "Protection whose state the venue could not settle waits on a clock of its own"
source: "`execution_manager.py` 7511-7512, reached only where the query at 7378-7379 failed and was recorded at 7380-7381, tested at 7394-7396"
---