doyle -> liam, hertz, todlando. RULED:
1. A6c-2 ACCEPTED: run 1 1968 ms empty, run 2 2125 ms populated, delta 157 ms composite (4 Assert-Owned walks + 2 removes), never split; parse control 2/0 with its caveat recorded (reconstructed truncation, not the dead bytes). F-A5-1 ACCOUNTING IS CLOSED, not solved: every candidate for A5's 2.775 s is measured and dead (hash 83 ms warm, edition refuted, populated set 157 ms); bring-up stays UNPARTITIONED with hertz's bound (>= ~0.83 s) beside it; the write invocation is <= ~2.1 s cold on this store populated, so the ~3.0 s write leg is dead by arithmetic AND by measurement. No further arm on this term: todlando's per-invocation logging is the instrument that answers it in the field, and it ships regardless.
2. hertz's three arms ACCEPTED in his ordering (Arm 1, Arm 3, Arm 2), all three filed before written, each with its opposite-polarity control, and a Windows lane that FAILS LOUDLY when skipped. Arm 1 is a lock, not evidence, as he says.
3. Arm 3 prediction REFUTED FROM SOURCE before it is written, as he invited: Describe's hygiene at windows.rs:104 reads (Is $rule 'Enabled' 'True') -and Direction Inbound -and Action Allow, so a pair created with -Enabled False fails hygiene and verify returns false. Predicted GREEN at head. Keep the cell as the lock; note that -Enabled False is an analogue of "persistent but not effective", not the GPO-override case, and say so in the cell's name.
4. Rider criterion 5 AMENDED BY REPLACEMENT (hertz's register line): every wall carries its exit code and a post-state census proving the work happened; a wall without both is not a measurement; brace balance or a parse-only check runs BEFORE the invocation. liam's 209/166 ms void is the specimen.
5. Box sequence: liam's 2011 read is done and struck; the box is hertz's now. hertz posts a fresh capture start line; todlando dials 29472 then 29471 once, his 03:10:33Z command verbatim with the control prepended. Nothing else runs on either box until hertz names the outcome.
6. Phase 2 is designed and posted (#304 comment 5643188052): ufw backend on kitsubito, default-ALLOW with one dropped port, NEEDS-OPERATOR for the posture write; nft backend refuses the host by design (nft_input, one input chain). hertz: cells 0 and 1 are read-only and may run on your word after the capture; the posture write waits for the operator.