2026-10-28 — The product thinker asked on 2026-10-28 for the machine's capacity to be used, so load.preflights now takes a whole number from 1 to 4 (MaxPreflightSlots rises from the 2 of the trial in dcn-2610161814279204), and above one slot a preflight queued at its race gate takes no first-gate slot until its race run starts (iss-2610282016250805). The grounds: one race run at a time, kept by the race gate, and the load wait limit stay the bounds; each stage's go test -p is still the cores divided among the slots, never below a quarter of them; and the count is the person's own machine setting, never a repository's, one by default.

Frontmatter

.abcd/work/decisions/dcn-2610282040085403-the-product-thinker-asked-on-2026-10-28.md
open on GitHub ↗ · commit history ↗

mentions2

• dcn-26101618142792042026-10-16 — The product thinker approved a measured trial of two preflights in their test stages at once, with the race stage kept to one at a time; the default stays one, and a person may raise it only for their own machine (load.preflights in ~/.abcd.noindex/config.json, or ABCD_LOAD_PREFLIGHTS), never from a repository file. So the setting takes 1 or 2 and nothing more: 3 and 4 are refused, saying the limit rises once a measured trial supports it. At the default of one the preflight runs exactly as before, its race gate opening at once.
• iss-2610282016250805The load gate leaves the machine idle: a make preflight queued at its race gate still counts as Busy at the first gate, so with load.preflights=2 one preflight running its race stage and a second waiting idle at the race gate fill both slots and every other preflight waits. Observed 2026-10-28 20:02-20:15Z: four preflights queued, one test stage running, load 13 on 16 cores. MaxPreflightSlots also caps the setting at 2.