What registering one creates
Registering a name creates, together: the queue submitted work waits in, the priority line cancellations and changes wait in, a queue that only tests write to, a record of its orders both open and closed, and a ledger of what has been spent and held. News from the venue arrives on queues made alongside those.
It also starts the one worker that will serve all of it. Registering a name that already exists creates none of this again: it re-registers at the venue and returns.
An account can be registered with its worker paused. Its worker exists but sleeps through every pass, which leaves recovery free to rebuild its records first — though recovery itself does reach the venue in that window, cancelling orders left over and, in one narrow case, sending again an order meant to close a position out. One the venue still has working is left alone.
What is shared anyway
Not everything is per-account. Some lists are shared by every account in the running host, which is why a request name already in use under one account is refused under another.
Holdings are counted under a trade and an account together, so the same trade name under two accounts is two separate holdings. On a real exchange, credentials are stored against the account name and used to sign that account's calls; a venue replaying recorded activity accepts them and never uses them.
Related
Source evidence
---
row: P2-12
baseline: 49aa659
created: 2026-09-24 20:13 UTC
modified: 2026-11-09 13:45 UTC
evidence:
- claim: "An account named by nothing at all is refused before any of the rest"
source: "`execution_manager.py` 812, then 813-814"
- claim: "Asking whether an account is held reads the one store of them"
source: "`execution_manager.py` 850"
- claim: "Registering a name creates its queues, its state and its ledger together"
source: "`execution_manager.py` 823-830, with two further queues made alongside at 581-584"
- claim: "Venue news arrives on one of those rather than the queue named in the constructor"
source: "`execution_manager.py` 3211 from `praxis/trading.py` 1757, the named one written only at `execution_manager.py` 3116"
- claim: "It also starts the one worker that will serve it"
source: "`execution_manager.py` 832-836"
- claim: "Registering a known name again re-registers it at the venue and returns, creating none of the account's own state again"
source: "`trading_inbound.py` 128-130, the manager never entered, though a replaying venue does reset its balance book at `replay_venue_adapter.py` 116"
- claim: "The refusal that raises is reserved for a direct call on the manager"
source: "`execution_manager.py` 816-818, the way in returning before it at `trading_inbound.py` 128-130"
- claim: "An account can be registered parked, its worker sleeping each pass"
source: "`execution_manager.py` 831, read by the worker at 3903-3905, cleared at 3670, then 3671 into 3672"
- claim: "Recovery acts on the venue while it is parked, cancelling a stray by one call or the other"
source: "either `praxis/trading.py` 978-982 for a linked pair or 984-988 otherwise"
- claim: "A flatten is re-sent only where the policy calls for it and several checks have all fallen through"
source: "`praxis/trading.py` 600 into the policy test at `execution_manager.py` 7912-7916, reaching 8255 only where every later check falls through, and the send itself at 7707 only past the further checks inside it"
- claim: "A flatten the venue still has working is left in place, not re-sent"
source: "`execution_manager.py` 7984-7994"
- claim: "The repair sweep reaches the same send by a call of its own, only where the policy calls for it and no such order stands already"
source: "`execution_manager.py` 7114, then 7115 into 7116, or 7118-7122 and 7136-7137, reaching the route at 7139 unless either test returns instead"
- claim: "Holdings are keyed by trade and account together"
source: "`trading_state.py` 482-491"
- claim: "On the exchange adapter, credentials are stored against the name and used to sign its calls"
source: "`binance_adapter.py` 444, loaded at 721 and signed with at 725"
- claim: "A replaying venue takes the same argument and never reads it"
source: "`replay_venue_adapter.py` 113-116"
- claim: "Some registries are shared across accounts, so a request name in use anywhere is refused"
source: "`execution_manager.py` 693-697 with the refusal at 3452-3457"
---