2026-09-15 15:58:24
Anonymous:
Clarify current readiness and station versus home fixture scope
hold the flood/mechanical interfaces and opening quantities.md ..
@@ 29,7 29,7 @@
### Boundary order
1. **Edit preview:** in the fully paused journal, accessible port direction/type and each possible concurrent demand state are checked. Invalid or over-supply proposals refuse without changing the current links. Physical pickup, mounting and removal remain live-world actions.
-
2. **Ordinary hold:** each automatic actuator checks its own readiness and source/actuator shared valid-target condition. Failure holds that actuator ready; it creates no launch or downstream delivery and does not block another path.
+
2. **Ordinary hold:** each automatic actuator checks its own readiness and source/actuator shared valid-target condition. Failure leaves that actuator’s current readiness unchanged: a recovering actuator stays unready, while a ready actuator without a valid target stays ready. It creates no launch or downstream delivery and does not block another path.
3. **Launch commit:** that actuator seals one selected target and spends one readiness as its external event starts. The physical launch executes once and cannot retarget.
4. **Descendant delivery:** every receiving branch checks its own link, type, readiness/storage, target, heat state and allocated threshold when the packet arrives. Refusal affects only that branch and refunds no already committed upstream state.
5. **Finite route:** after complete-action heat has been reserved at commit, an Arc route, projectile bank, penetration segment, fragment fan or bloom spends only its named geometry/body allowance. Missing line, obstruction or exhaustion ends it visibly; heat is never charged again per hop, contact or descendant and cannot secretly shorten an accepted effect. A descendant cannot refill the allowance, readiness or power that created it.
