The pass in between
Between the turning and the queue a report is put through the accounting, but only where the account's wiring is published, and that pass returns before working the report through where its command has no context registered. The queue takes the report either way.
What it does not read
The names a start gathers to decide what to send again are read nowhere between the turning and the queue.
Where an outcome is dropped
An outcome for an account with no queue is dropped before it is turned into reports at all.
Related
- How an undelivered outcome is replayed
- Outcomes that never come back
- An outcome waiting on a strategy
Source evidence
---
row: P5-05
baseline: 49aa659
created: 2026-11-05 16:22 UTC
modified: 2026-11-09 10:25 UTC
evidence:
- claim: "Each report the turning returns is put on the account's queue"
source: "`praxis/launcher.py` 2988 and 2992"
- claim: "The pass that moves the figures between them runs only where the account's wiring is published"
source: "`praxis/launcher.py` 2985-2986 and the test at 2989 before 2990, with 2992 standing outside it"
- claim: "That pass reads the command's registration under the registry's lock and takes the context off it, or nothing where no registration stands"
source: "`praxis/launcher.py` 2896, then 2897"
- claim: "It returns without working the report through where its command has no context registered"
source: "`praxis/launcher.py` 2902 before the return at 2916, against the working through at 2919"
- claim: "A working through that reports a failure returns as well, leaving the figures where they stood"
source: "`praxis/launcher.py` 2927 into 2936"
- claim: "An outcome for an account with no queue is dropped before it is turned into reports"
source: "`praxis/launcher.py` 2974-2983, which returns rather than reaching 2988"
- claim: "The names a start gathers from the spine are read nowhere between the turning and the queue"
source: "`praxis/launcher.py` 2988 and 2992, with no read of the gather at 1735-1736 between them"
---