**Status.** Conditional first-pass operating candidate. It makes the advertised opening, Counterwall and heat-lance examples determinate enough for paper accounting. The owner-selected directions are connected reusable parts, mostly automatic ordinary fire, manual specials, limited carried oxygen, unlimited ship oxygen, one shared carrying capacity and carried-property return. The **10 C / 4 A comparison baseline, four-part starting inventory, every amount and threshold, controller limit and fixture detail introduced here are proposed**, replaceable and unvalidated. This article adds no implementation, asset, balance result, campaign claim or answer to any of the five pending owner questions.

Support one **independent ordinary launch path** in a first-pass rig: one event source names one ordinary launch actuator whose readiness, shown reach and selected nearest visible valid target gate and commit that launch exactly once. Threat Sensor or deliberate-grounded-movement Stride may source that one path. Stride may also coexist with Sensor when its separate link ends in a non-launch response such as a configured Capacitor→Barrier release. Fork may copy the committed wave to other compatible descendants, and manual or derived paths such as Projector impact → Dynamo → Arc remain legal; neither is an extra independent ordinary launch. In normalized packet examples a committed Dynamo or either stated Cycler response carries **2 usable units (U)**, Fork divides usable payload in a fixed output order without amplification, Capacitor holds **4 U**, and chosen manual release spends **2 U** only after its first receiver accepts. Failed later receivers never rewind an upstream commit. For the proposed opening comparison, use **10 C / 4 A**, a **12 O** suit tank, **8 O** ordinary canister, **12 O** prepared canister, continuous base drain of **1 O per 30 seconds**, transfer of up to **3 O per 30 seconds** while breathing continues, and a player-set suit reserve mark defaulting to **4 O**. These numbers determine the following paper cases only; they prove no route safe or build balanced.

An ordinary launch path consists of one event source, one named ordinary launch actuator and any compatible non-controller parts between or after them. In the opening path, Threat Sensor observes its shown arc and the designated Pulse Projector owns reach, readiness and target validity. While Projector is ready, the nearest visible valid hostile inside the intersection of Sensor arc and Projector reach is selected. Positioning may change that candidate until launch commits. No candidate holds the path ready; it does not spend readiness, emit a trigger or create a wave. At commitment, the target and Projector readiness spend seal one launch reservation and start one external event. When that wave reaches the designated Projector, it executes the reserved physical launch once as part of the same event; the projectile never retargets.

Fork behind Sensor does not create another ordinary launch. It carries the committed bare trigger/wave to the already designated Projector branch and copies it to the other outputs. The designated Projector does **not** recheck the readiness it has just spent, refuse its own sealed launch or shoot again when the packet reaches it; it executes that one sealed launch. Other descendants still check independently. A ready Barrier can therefore respond on the same wave; an unready Barrier refuses locally and queues nothing. A downstream Arc driven by charge from a Dynamo clamp is likewise a descendant action in the existing wave, not a second controller event. Manual Trigger and chosen manual Capacitor release remain independent manual sources under their own rules.

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.

5. **Recovery:** the ordinary actuator becomes ready only through its stated world time. Readiness completion creates no target, trigger or wave.

| Arc Emitter | Minimum **1 U** charged trigger; it spends its delivered packet on that one action |

4. If both pass, Fork divides the amount as evenly as whole U allow: output 1 receives the larger share when odd, output 2 the smaller. Thus 1 U divides 1/0, 2 U divides 1/1 and 3 U divides 2/1. Total assigned never exceeds input.

- **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 valve accepts while compressor refuses, the vessel may reach at most ordinary-full and remains ordinary-full/partial, never prepared-full. During an accepted compression cycle, cancellation or lost power preserves the exact amount already in the vessel; an 8–11 O vessel is labelled partial with a last completed amount and can resume. No incomplete cycle awards the prepared-full state.

- **Stage/commit:** preview arrows → hand-cycle selector → final detent commits mode. Afterward, pressing test admits one pulse at the input contact; the pulse commit is separate from mode commit. A valid forward test visibly produces B; reverse produces A.

| **Station Room / Encounter inventories** | Reference the R26/R33 cards and normalized rig outcomes where useful. Add no room, encounter, major mechanism, part source or route. |

| **Player Information And Options** | Represent exact 0–4 U storage, full/partial/saturated, branch blocked versus sub-threshold, first-receiver pre-release refusal, actual O amounts and the four fixture active/incomplete states. The unsupported-topology refusal is a structural legality count only: it names the second source-to-ordinary-launch path that exceeds the one-path envelope. It predicts no target, readiness, receiver result, payload path or future outcome and therefore is not an assembled-graph outcome simulation; ordinary direct-link validity remains separately local. Presentation/default/accessibility remain Information34-owned. |

The mechanical handoff is therefore finite: ordinary launch-source and designated-actuator identity, selected target/readiness at the single commit, one wave identity, per-branch block/allocation/refusal, exact stored U, exact vessel O/fill label, installed/carried fixture location, current stage, last committed checkpoint, fixed/reversible mode and whether an observation was locally performed or separately captured. It is not a complete scheduler or exhaustive engine state matrix.

**Candidate choice.** Use one independent ordinary launch path sourced by Sensor or Stride, conservative fixed-order Fork division, hold-and-vent Capacitor storage, fixed 2 U manual release, and the one provisional opening quantity sheet. This keeps Stride's non-launch coexistence, existing manual and derived multi-actuator builds while making all eight traces determinate.

**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 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.

The article contains five requested deltas, one quantity sheet, four existing local interface cards and exactly eight paper cases. It keeps the proposed comparison **10 C / 4 A**, existing bridge **2 C** and regulator **2 C**; proposes suit **12 O**, ordinary/prepared vessels **8/12 O**, base drain **1 O/30 s**, transfer up to **3 O/30 s** with a 12 O ceiling/empty stop, reserve default **4 O**, both new assembly values **2 C**, Dynamo **2 U per eligible wave regardless of batch count**, conductive response **2 U charge**, pressure response **2 U force**, Capacitor **4 U** and release **2 U**. Case arithmetic accounts for active versus inactive C/A, one Fork/object instance, gas transferred/breathed and retained at both bounds, material consumption, charge allocation/storage/vent/release and upstream versus downstream commitment. Sensor/Stride launch alternatives, legal non-launch coexistence, single launch/readiness commit, once-per-wave, no readiness-created event, first-receiver pre-release refusal, sole-pre-allocation-candidate full payload, local test/evidence/walking separation and completed-work persistence remain intact.