At the door
Praxis refuses everything while it is shutting down, and before it has been started at all.
Then the account must have finished starting. A name never registered fails this test too, so an unknown account is turned away here rather than deeper in, as is one whose start failed โ it never joins the list of started accounts.
An account that fails later stays in that set, and a later refusal catches it.
As the request is built
A request name supplied with the work must not be empty, must be long enough to build an order name from, and must not already be in use anywhere, since that register spans accounts.
The request then checks itself as it is built, on many grounds โ among them an amount that is not positive, a time without a zone, a trading pair left blank. How its parts fit together is checked on many more, from an order type the chosen way of working disallows, to protective prices on the wrong side of the opening one. The venue's own filters are not applied here; none are passed in.
The execution mode must be switched on for this host. By default only the plain single order is.
Last, the queue must have room. A full one refuses rather than waits.
After them
Only then is the acceptance written. Even then the work may not be queued: if the account has failed by that point, it is ended there with a rejected report instead. Work turned away at a gate leaves no record behind at all.
Related
Source evidence
---
row: P2-24
baseline: 49aa659
created: 2026-09-24 21:11 UTC
modified: 2026-11-09 13:28 UTC
evidence:
- claim: "Work is turned away while Praxis is shutting down"
source: "`praxis/trading.py` 1878-1880"
- claim: "It is turned away before Praxis has been started"
source: "`praxis/trading.py` 822-825"
- claim: "It is turned away for an account that has not finished starting, which an unknown name also fails"
source: "`praxis/trading.py` 836-838, the only entry to that set being 606-608"
- claim: "An account that failed its start never joins that set"
source: "`praxis/trading.py` 623 looking the account up at `execution_manager.py` 3639, then 3640 into 3641, or setting the flag at 3643, the only entry to that set being `praxis/trading.py` 606-608"
- claim: "An account poisoned later stays in the set, so the manager's own refusal is what catches it"
source: "poisoned at `execution_manager.py` 4026, refused at 3434-3436"
- claim: "A supplied request name that is empty is refused"
source: "`execution_manager.py` 3446-3448"
- claim: "One too short to build an order name from is refused next"
source: "`execution_manager.py` 3450 into `generate_client_order_id.py` 105-110"
- claim: "One already in use anywhere is refused after that"
source: "`execution_manager.py` 3452-3457"
- claim: "The command checks itself as it is built, on many grounds"
source: "`praxis/core/domain/trade_command.py` 79-116, and a mismatched parameter type at 118-124, raised from `execution_manager.py` 3461"
- claim: "How its parts fit together is checked on many more"
source: "`execution_manager.py` 3479 into `validate_trade_command.py`, from an order type the mode disallows at 195-200 to bracket prices on the wrong side at 382-394"
- claim: "The venue's own filters are not applied here, since no filters are passed"
source: "`validate_trade_command.py` 143-146, never entered from `execution_manager.py` 3479"
- claim: "An execution mode switched off on this host is refused"
source: "`execution_manager.py` 3481-3495, the set defaulting to single-shot alone at `trading_config.py` 105-107"
- claim: "A full queue is refused last, and fails closed"
source: "`execution_manager.py` 3497-3511"
- claim: "All of these raise before the accept is written"
source: "the accept at `execution_manager.py` 3515-3525"
- claim: "Work for an account already failed by that point is ended there rather than queued"
source: "`execution_manager.py` 3531-3547, rather than the queue put at 3550"
---