hold the flood/mechanical interfaces and opening quantities.md ..
@@ 35,7 35,7 @@
Stride Switch is an external event source with its accepted deliberate grounded-movement gate. **Stride→Projector may replace Sensor→Projector as the rig's one independent ordinary launch path**: only the astronaut's qualifying traversal emits the Stride packet, then the designated Projector must be ready and have a valid selected target for the launch to commit once. Conveyor motion, shove and recoil remain invalid. Separately, Sensor→Projector may remain the sole ordinary launch while Stride uses a different input to trigger a configured Capacitor release into Barrier. That Stride wave retains its identity; Capacitor and Barrier apply their existing readiness/charge checks. The coexistence is legal because the Stride branch ends in a non-launch descendant and shares no input. Two sources connected to the same single Projector input, or Sensor→Projector plus Stride→a second Projector, remain unsupported.
-
For this first pass, a rig preview supports at most one independent ordinary launch path and one designated ordinary launch actuator. A second Sensor, a second separately target-seeking Projector, Sensor→Projector plus Stride→another ordinary launcher, or any two source-to-launch paths in the same active rig is labelled **unsupported by the current content envelope** before the final edit commits. Other external sources and legitimate descendant actions do not count toward that limit. The objects remain legal possessions and may be packed, used in separate rigs or installed elsewhere; nothing is consumed. This is a proposed content limit, not a physical impossibility or permanent owner decision. It sacrifices simultaneous independently targeted ordinary fire and meaningful duplicate-controller builds in exchange for one target/readiness owner and a bounded first-pass interaction surface. Later work could lift it only with an explicit arbitration rule, duplicate sources and representative encounter/interface coverage.
+
For this first pass, a rig preview supports at most one independent ordinary launch path and one designated ordinary launch actuator. A second Sensor feeding another ordinary launcher, a second independently target-seeking ordinary Projector, Sensor→Projector plus Stride→another ordinary launcher, or any two independent ordinary source-to-launch paths in the same active rig is labelled **unsupported by the current content envelope** before the final edit commits. Other external sources and legitimate descendant actions do not count toward that limit. The objects remain legal possessions and may be packed, used in separate rigs or installed elsewhere; nothing is consumed. This is a proposed content limit, not a physical impossibility or permanent owner decision. It sacrifices simultaneous independently targeted ordinary fire and meaningful duplicate-controller builds in exchange for one target/readiness owner and a bounded first-pass interaction surface. Later work could lift it only with an explicit arbitration rule, duplicate sources and representative encounter/interface coverage.
### Boundary order
@@ 45,7 45,7 @@
4. **Descendant delivery:** every **other** receiving branch checks its own link, type, readiness/storage, target and allocated threshold when the packet actually arrives. Refusal affects only that branch, creates no event and refunds no already committed upstream state.
5. **Recovery:** the ordinary actuator becomes ready only through its stated world time. Readiness completion creates no target, trigger or wave.
-
The credible smaller rule is **direct Sensor → Projector only** for ordinary fire, with no Fork branch on that event. Manual specials and Projector → Dynamo → Arc descendants still work. This is cheaper to explain and removes branch arbitration from ordinary fire, but deletes the four-space sensor-timed Barrier choice and reduces Fork's early expressive value. The chosen envelope keeps that one branch without opening multiple independent ordinary launches.
+
The credible smaller rule is **one direct Sensor → Projector or Stride → Projector path** for ordinary fire, with no Fork branch on that event. Manual specials and Projector → Dynamo → Arc descendants still work. This is cheaper to explain and removes branch arbitration from ordinary fire, but deletes the four-space sensor-timed Barrier choice and reduces Fork's early expressive value. The chosen envelope keeps that one branch without opening multiple independent ordinary launches.
## 2. Fork allocation, storage and committed loss
@@ 113,7 113,7 @@
### Declared opening arithmetic assumptions
-
For the paper cases only, treat the currently walked opening as: ship/R01→R02 board **one 30-second interval**; R02→R03 rack **one**; the same return **two**; one fastener stage **two**; Fork install or reclaim **one each**; bridge pickup **one**. No enemy delay, displacement, tether, door wait, wrong turn or unseen route is included. Under base drain alone, direct out-and-back plus one fastener and bridge pickup consumes **7 O**. Adding both Fork installation and reclaim consumes **9 O**. A full 12 O suit would therefore show 5 O or 3 O respectively before any combat cost. Crossing the proposed 4 O reserve is information, not proof that return fails or succeeds. For each 30-second hand check, debit the interval's 1 O breathing and then move up to 3 O subject to the same continuously enforced tank/vessel boundaries; this ordering is arithmetic notation, not a pause in breathing.
+
For the paper cases only, treat the currently walked opening as: ship/R01→R02 board **one 30-second interval**; R02→R03 rack **one**; the same return **two**; one fastener stage **two**; Fork install or reclaim **one each**; bridge pickup **one**. No enemy delay, displacement, tether, door wait, wrong turn or unseen route is included. Under base drain alone, direct out-and-back plus one fastener and bridge pickup consumes **7 O**. Adding both Fork installation and reclaim consumes **9 O**. A full 12 O suit would therefore show 5 O or 3 O respectively before any combat cost. Crossing the proposed 4 O reserve is information, not proof that return fails or succeeds. For each hand check, account for breathing and transfer over the actual time before a ceiling or empty stop; full-interval totals apply only while transfer continues for that whole interval. Breathing continues after transfer stops.
These assumptions explain arithmetic; they are not final action timings, safe-route certification, balance, comfort, campaign duration or a promise the R02/R03 route remains available after death.
@@ 122,7 122,7 @@
### Ship collar receiver
- **Source/input/control:** fixed ship power, the existing collar monitoring bus and fixed maintenance poll control provide one bare trigger to a seated Fork. Fork output 1 reaches the addressed poll gate; output 2 reaches the display latch. The sensor value returns through the fixed collar bus, never through Fork.
-
- **Ready/refusal:** the fixture must be commissioned, the one known address selected, Fork seated, bus powered, poll gate neutral and display latch cleared. Each branch checks independently. A missing Fork or both branches blocked refuses at the control. One accepting branch may act, but a dated receiver reading requires both the poll sample and display latch for the same poll.
+
- **Ready/refusal:** the fixture must be commissioned, the one known address selected, Fork seated and bus powered. Poll-gate neutrality and a cleared display latch are separate branch-readiness conditions; each branch checks independently. A missing Fork or both branches blocked refuses at the control. One accepting branch may act, but a dated receiver reading requires both the poll sample and display latch for the same poll.
- **Stage/commit:** pressing the control starts one world-time poll wave. Poll-gate opening commits that branch; display arming commits its branch. The fixed bus sample commits only when the poll gate reaches its sampling detent. A simultaneously armed latch then holds that sample for direct observation; capture into evidence is a separate world-time action.
- **Incomplete/interrupted:** if poll accepts but display refuses, the gate performs one addressed sample into a temporary local buffer marked **unlatched**. Only that incomplete-status mark is shown: the buffered value is not player-readable, cannot be captured and is not a completed dated reading. If display arms but poll refuses, it times out empty. Power loss or cancellation before sampling detent yields no sample; after detent it leaves only that unreadable unlatched buffer until clear/retry. Neither outcome proves collar pressure, sensor health, route or safety.
- **Recovery/removal:** clearing the latch/buffer discards any unlatched sample, then restored readiness permits a wholly new poll; incomplete branches never secretly pair across attempts. Fork may be reclaimed only after the active poll is cancelled or settled. Reclaiming that same instance darkens future polling but does not erase a completed observed/captured reading. Lost power ends live value; stored evidence remains dated.
@@ 193,7 193,7 @@
**Opening arithmetic:** under the declared no-encounter assumptions, out/back + one fastener + bridge pickup consumes 7 O, taking a full suit from 12 to 5. Installing and reclaiming Fork adds two intervals and reaches 3 O, below the proposed 4 O reserve mark. That mark commands nothing, may not be presented as a route estimate and predicts no safety; the player may transfer, leave Fork, return after the fastener or accept further risk.
-
**Incremental transfer:** suppose the suit is 4 O and the selected prepared canister 12 O. One 30-second coupling interval breathes 1 O and moves 3 O: suit becomes 6, canister 9. A second becomes suit 8, canister 6. Six moved, two were breathed, and total remaining oxygen fell only by those two. At the ceiling boundary, suit 11/canister 5 becomes suit 12/canister 3 after one interval: breathing spends 1, only 2 of the possible 3 transfer, and the untransferred unit remains in the vessel. At the empty boundary, suit 5/canister 1 becomes suit 5/canister 0: one is breathed and only the last one can move. Back aboard, ordinary refill can raise a 6 O vessel to ordinary-full 8, not prepared-full 12; another completed bench cycle is needed to restore the four-unit surplus. None of this includes combat delay or certifies the return.
+
**Incremental transfer:** suppose the suit is 4 O and the selected prepared canister 12 O. One 30-second coupling interval breathes 1 O and moves 3 O: suit becomes 6, canister 9. A second becomes suit 8, canister 6. Six moved, two were breathed, and total remaining oxygen fell only by those two. At the ceiling boundary, starting suit 11/canister 5 reaches suit 12/canister 3.5 after 15 seconds: 1.5 O transfers and 0.5 O is breathed, then transfer stops immediately at the ceiling. If the remaining 15 seconds pass without a new transfer, breathing leaves suit 11.5/canister 3.5. The stopped transfer does not keep topping up the tank. At the empty boundary, suit 5/canister 1 becomes suit 5/canister 0: one is breathed and only the last one can move. Back aboard, ordinary refill can raise a 6 O vessel to ordinary-full 8, not prepared-full 12; another completed bench cycle is needed to restore the four-unit surplus. None of this includes combat delay or certifies the return.
### F. Reclaim an area-granting assembly without duplication
@@ 242,7 242,7 @@
**Accepted cost.** The controller envelope forbids potentially expressive duplicate independent ordinary-launch rigs in first-pass content. Fork output order can matter, a sub-threshold share can be visibly lost, and vented overflow may feel punitive. Fixed 2 U release reduces fine control. Exact oxygen numbers may over- or under-pressure the opening, and 2 C assemblies can make area growth feel like a mandatory packing ladder. Four local cards add authored interruption and recovery states. None of those costs is validated.
-
**Smaller supported variant.** Keep direct Sensor→Projector as the only ordinary path, the quantity sheet and fixed storage policy, and omit Fork branching from ordinary fire. Counterwall, Cycler and paid-rewire descendants remain. This loses the opening's Sensor→Fork→Projector+Barrier control trade and leaves less evidence that one part can reshape both infrastructure and personal rigs; it does not delete any accepted part or rig source.
+
**Smaller supported variant.** Keep one direct Sensor→Projector or Stride→Projector ordinary path, the quantity sheet and fixed storage policy, and omit Fork branching from ordinary fire. Counterwall, Cycler and paid-rewire descendants remain. This loses the opening's Sensor→Fork→Projector+Barrier control trade and leaves less evidence that one part can reshape both infrastructure and personal rigs; it does not delete any accepted part or rig source.
**Open rather than invented.** Duplicate quantity/stacking, multiple independent ordinary-launch arbitration, final target override, odd payload sources beyond the stated rule, damage/strength/timing, exact encounter delays, every overflow/port/geometry variant, final screens and accessibility equivalents, fabrication versus found parts, retained charge across death, survivor air/mortality, population continuity, save policy, completed-station stabilization and all campaign/economy tuning remain with their owning decisions. The five pending owner questions are unanswered.
