Orders at several prices
A ladder rests all its rungs at once, so a resumed one has nothing left to plan or place. It comes back holding the rungs whose order has not ended, with the count already posted, and no timer. The pass finishes it only with no rung working, no hold standing, no change in flight and the count at its total — so one interrupted part-posted does not finish merely because its surviving rungs settle.
One whose change was in flight at the stop comes back with that change's stage set, for the same driver to carry on from.
Work fed out over time
A run fed out over time comes back at its recorded cursor. Where a schedule change was recorded, that plan's amounts and gap replace the original, and the timer comes from whichever of the progress mark and the change was written later.
Protection
What a restart makes of a bracket turns on what its pair was doing: one confirmed resting comes back as it is, one that never got out is sent, and one mid-change comes back unknown for the watch.
The hold it comes back under
A scheme's hold is rebuilt from the freeze marks replayed, under the precedence the running one keeps: winding up outranks a protection freeze, which outranks a failed-slice freeze. A protection freeze wins whatever order the marks arrived in, and no thaw lifts it — so a restart cannot resume a scheme running where the live one would have held it.
Related
- The event spine
- Work fed out over time
- Orders at several prices
- What a restart puts back of a bracket
Created 2026-10-13 11:25 UTC · Last modified 2026-10-14 08:05 UTC
Source evidence
---
row: P4-46
baseline: 49aa659
created: 2026-10-13 11:25 UTC
modified: 2026-10-14 08:05 UTC
evidence:
- claim: "A ladder comes back holding the rungs whose order has not ended, with the count already posted"
source: "`execution_manager.py` 1359-1361 into 1371-1376"
- claim: "It comes back with no timer, and the pass finishes it only with no rung working, no hold, no change in flight and the count at its total"
source: "`execution_manager.py` 1378, weighed at 6352-6372"
- claim: "One whose change was in flight comes back with that change's stage set"
source: "`execution_manager.py` 1453 and 1464"
- claim: "A run fed out over time comes back at its recorded cursor"
source: "`execution_manager.py` 1979"
- claim: "A recorded replan's amounts and gap replace the original ones"
source: "`execution_manager.py` 1963-1969 and 1975-1977"
- claim: "The timer is taken from whichever of the progress mark and the replan was written later"
source: "`execution_manager.py` 1981-1985 into 2050-2057"
- claim: "A scheme's hold is rebuilt under the precedence the running one keeps, a protection freeze winning whatever the order and no thaw lifting it"
source: "`execution_manager.py` 282-289, called at 1987"
---