diff --git a/.claude/memory/rules.md b/.claude/memory/rules.md index 2018bf27..75d373e0 100644 --- a/.claude/memory/rules.md +++ b/.claude/memory/rules.md @@ -153,3 +153,17 @@ him -> the tag, on his word. - **POST is as v3's works.** Not reproducing v3's tests AS WRITTEN, or a parity mismatch, is THE failure. - Order given: inspect the debug (EMERGENCY) build first, then write the design for the failure-triggered diagnostic build -- for his ruling, before building. + +## A long stage may run in the background, but only alone (Captain Bob, 2026-11-18) + +A protocol stage that takes longer than one foreground command (600 s at most) may run in the +background, on one condition: **nothing else runs at the same time**, no other background process +of any kind, the docs stage included. Captain Bob: "Aarch64 bg is fine as long as there is no other +background process running including docs. In fact that might generalize too." + +So: +- **One stage at a time,** foreground or background. A background stage is waited for before the + next stage, or anything else, starts. +- **Still one QEMU at a time.** +- **Today this covers** `accept-aarch64` (401 to 429 s for the boot plus its session) and `docs`. + Any other long stage runs the same way.