A drain's --pace and --sub-agents reach only the lane opened in its first move; later lanes resolve their pace again from configuration, so the old drain's first lane ran 10080/0 with six sub-agents and its next ran 120/300 with two.

Frontmatter

.abcd/work/issues/resolved/iss-2610161015417715-a-drain-s-pace-and-sub-agents-reach-only.md
open on GitHub ↗ · commit history ↗

References1

• itd-2610161016401115Drains run unattended and visiblyrelated

mentions3

• dcn-26101610403991172026-10-16 — A drain's pace reaches every lane (facilitator-on-delegation, drain-many-accounts): a drain carries its resolved pace and sub-agent ceiling into every lane it opens, and a running drain takes a new --pace or --sub-agents, recording them in its state and applying them from the next lane it opens and the lane in progress's next stage; a handed-back issue whose record blob on origin's default branch has changed is eligible again, and a finished handed-back run no longer passes its issue over (grounds: a setting the person gives is the drain's for its whole life, and a changed record is a new question; iss-2610161015417715, iss-2610161015457468).
• dcn-26101707504116282026-10-17 — A running drain's new pace and its re-admissions (facilitator-on-delegation, drain-many-accounts, spc-2610161044461448 step 16; refines dcn-2610161040399117): every lane a drain opens starts on the pace stored in the drain's state, with the layer and origin the drain resolved, never on what the configuration resolves at the lane's start; a running drain takes --fix-rounds as well as --pace and --sub-agents, since the fix rounds are the pace's fourth number set alongside it (ruling DR1), each number named replacing the stored one and the rest kept, written to the drain's state and to each in-progress lane's run pace, which that lane's next stage reads; a route keeps the blob of the issue's record on origin's default branch, and the drain re-admits a handed-back issue once that blob differs, an answer taken before the hand-back deciding nothing; an issue run whose lane was handed back is over for the drain alone, so the drain neither passes the issue over for it nor resumes it and opens a new run, while abcd build keeps resuming it as before; without origin nothing records a change, so a handed-back issue and an issue whose run here is over stay passed over (grounds: a setting the person gives is the drain's for its whole life; a changed record is a new question, read from the same blob the tombstone carries; a change confined to the drain leaves build's resume untouched; iss-2610161015417715, iss-2610161015457468)
• spc-2610161044461448drain-many-accounts