2026-09-10 11:12:02
Anonymous:
Outcome47: replace single-launch controller with multi-output power/heat and finite echo return boundary; align affected examples
hold the flood/mechanical interfaces and opening quantities.md ..
@@ 1,20 1,20 @@
# Hold The Horde — Mechanical Interfaces And Opening Quantities
-
**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.
+
**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, carried-property return and reset of temporary combat upgrades on every return home. The **10 C / 4 A comparison baseline, four-part starting inventory, every amount and threshold, power/heat 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 pending owner question.
| [Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station) | `fa385ca5f2d530a1ac1fc0dfcb4e8926c920a66effd0e7e8f9574da032a6bcce` |
| [Death Shift And Rescue Continuity](/Hold%20The%20Flood/Death%20Shift%20And%20Rescue%20Continuity) | `577236e70c61bdf7c8af7a58ebdb982a4742fcfd16115f2b8dae6de93b3bd951` |
| [Player Information And Options](/Hold%20The%20Flood/Player%20Information%20And%20Options) | `61e0be4a01b4a6ac60da3dde999dff7c76422252aaade5cb614a1c6f63afda22` |
@@ 23,29 23,30 @@
## Candidate in one paragraph
-
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.
+
Support several **independent ordinary launch paths** when the mounted rig, carrying manifest and visible power budget allow them. Every automatic actuator owns its shown reach, target rule and readiness; each commits its own launch when ready with a valid target. Fork may also carry one committed event to compatible descendants. Repeated arcs, rebounds and returns spend a visible finite echo budget and add heat; a descendant cannot refill the budget, readiness or power that created it. Manual Trigger and chosen Capacitor release remain distinct manual sources. 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.
## 1. Supported controller and receiver envelope
### The proposed supported envelope
-
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.
+
An ordinary launch path consists of one event source, one named automatic actuator and any compatible changing or delivery parts between or after them. Threat Sensor observes its shown arc; each connected Pulse Projector or other automatic actuator owns its own reach, readiness and target validity. While an actuator is ready, the nearest visible valid hostile inside the intersection of source arc and actuator reach is selected. Positioning may change that candidate until this actuator commits. No candidate holds another path ready, spends its readiness or creates a shared reservation. At commitment, that actuator seals one target and spends its own readiness; its 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.
+
Several such paths may coexist. Sensor→Projector and Stride→a second Projector are legal if both mounted chains fit and the previewed simultaneous demand does not exceed the rig's visible power supply. Each checks and fires independently. The same is true of two automatic actuators behind a compatible Fork: the event is shared, but each receiver keeps its own readiness and target. One refusing branch never suppresses a ready sibling. 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.
+
Stride Switch emits only for its accepted deliberate grounded-movement gate. Conveyor motion, shove and recoil remain invalid. A qualifying traversal may therefore launch its connected ready actuator while a Sensor path independently watches another arc, or may end in a non-launch response such as a configured Capacitor→Barrier release. Shared physical inputs, port compatibility and target rules still apply locally; legal possession never guarantees that two plugs fit the same socket.
-
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.
+
The rig preview checks compatible links and total visible operating demand before a link edit commits. A proposal above supply refuses without changing the current links. A legal multi-output rig pays for its coverage in active space, carrying space, power and heat. Firing and returns add their stated heat; a hot component follows its inspected pause or weakening rule instead of a hidden global firing priority. Exact supply, draw, heat thresholds and cooling rates remain open quantities rather than a disguised single-launch cap.
### Boundary order
-
1. **Edit preview:** accessible port direction/type and the one-independent-launch topology are checked. Invalid or currently unsupported links refuse before world-time edit commitment.
-
2. **Ordinary hold:** the designated launch actuator checks readiness and the source/actuator shared valid-target condition. Failure holds ready; there is no event, wave or downstream check.
-
3. **Launch commit:** one selected target and one readiness spend seal one launch reservation as the external event starts. When the wave reaches the designated actuator, that reserved physical launch executes once as part of the same event; the branch cannot recheck or act again in this wave.
-
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.
+
1. **Edit preview:** in the fully paused journal, accessible port direction/type and total visible operating demand 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.
+
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. **Return:** an arc jump, projectile rebound or other named return spends one echo from that causal sequence and adds its stated heat. With no echo, target or heat headroom, the branch ends visibly. A descendant cannot refill the echo budget, readiness or power that created it.
+
6. **Recovery:** each ordinary actuator becomes ready only through its stated world time. Readiness completion creates no target, trigger or wave.
-
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.
+
The credible smaller tuning variant is a low-supply opening backplane that powers one ordinary path until the player installs a discovered supply assembly. It uses the same rules and makes the restriction a visible build cost rather than a universal topology ban. Whether the opening should begin that constrained remains an owner-facing quantity choice.
## 2. Fork allocation, storage and committed loss
@@ 88,6 89,10 @@
This article deliberately does not decide whether stored Capacitor charge survives death, living return, storage removal or another expedition boundary. Save/global04 must represent the actual amount and apply their accepted owning policy once that policy exists. No case below uses death to settle retained charge.
+
### Return effects and echo conservation
+
+
An external launch, manual activation, enemy strike or environmental event starts one causal sequence. A permanent part or temporary expedition upgrade may attach a visible finite **echo budget** to that sequence. Each named arc jump, projectile rebound or signal return spends one echo and adds its stated heat before it can revisit compatible descendants. With no echo, valid target or heat headroom, that branch stops. A descendant cannot refill the same sequence's echo budget, refresh the readiness already spent to create it or mint usable U from its own output. A later automatic firing cycle, new manual activation or separate enemy strike starts a new sequence with its own budget. Exact echo grants and heat values remain open; the conservation boundary does not.
+
## 3. Opening quantity sheet
### Proposed comparison quantities
@@ 157,19 162,19 @@
**Before:** active Sensor 1/1 → Fork 1/1 → Projector 1/1 + Barrier 1/1 is **4 C / 4 A**. Manual Trigger is inactive but still **1 C / 0 A**, so equipment uses 5 C. Projector is ready with one nearest visible valid hostile; Barrier is unready.
-
**Action:** Sensor and Projector gate one ordinary external event. At commit the target and Projector's one readiness spend seal one launch reservation. Fork carries that committed bare trigger/wave through the designated Projector branch; Projector executes the reserved physical launch once without rechecking the just-spent readiness, while Fork copies the wave to Barrier. Barrier independently refuses because it is unready.
+
**Action:** Sensor presents one bare trigger to both branches. Projector checks its own ready state and target, commits that target and spends its readiness to launch once. Barrier independently refuses because it is unready. Its refusal neither cancels Projector nor queues a later response.
-
**After:** one shot exists in the one wave. Barrier performs nothing, stores nothing and queues nothing; Manual still occupies 1 C. Barrier later becoming ready emits no event. The rig stays inside the one-independent-launch envelope because Barrier is a descendant response, not another target-seeking ordinary controller.
+
**After:** one shot exists in the one wave. Barrier performs nothing, stores nothing and queues nothing; Manual still occupies 1 C. Barrier later becoming ready emits no event. A second automatic actuator would be legal if its own links, space, power, heat, target and readiness passed; this four-A rig simply does not contain one.
-
### B. Eight-A heat-lance split, threshold and paid rewire
+
### B. Eight-A heat-lance split, threshold and paused link edit
-
**Before:** Sensor1 + Projector1 + Dynamo1 + Fork1 + Arc2 + Capacitor1 + Lens1 is **8 C / 8 A**. Sensor→Projector is the sole ordinary launch; Dynamo clamps to Projector output; its 2 U goes through Fork output1→Arc and output2→Capacitor. Both accept, Capacitor starts 0/4.
+
**Before:** Sensor1 + Projector1 + Dynamo1 + Fork1 + Arc2 + Capacitor1 + Lens1 is **8 C / 8 A**. Sensor→Projector is this rig's automatic launch path; Dynamo clamps to Projector output; its 2 U goes through Fork output1→Arc and output2→Capacitor. Both accept, Capacitor starts 0/4. The rules would allow another automatic actuator, but this manifest spends its eight spaces on branching, storage and conversion instead.
**Action 1:** the first committed Projector impact makes Dynamo emit exactly 2 U regardless of how many qualifying impacts that carrier batched in the wave. Fork divides 1/1. Arc meets its 1 U minimum and acts; Capacitor stores 1 U. It is partial and below the 2 U release threshold. As a separate paper alternative replacing output2→Capacitor, output2→Lens would give Lens only 1 U and refuse for insufficient share. It is not simultaneously connected, does not share Projector's already occupied input and creates no amplification.
-
**Action 2:** on a later valid ordinary wave Arc is unready before allocation, so Capacitor is the sole pre-allocation candidate and receives the full 2 U. It now holds 3/4. The player pays one world-time rewire, disconnecting Sensor from Projector before connecting Capacitor manual release→Lens→Projector, then selects a valid displayed Projector target.
+
**Action 2:** on a later valid ordinary wave Arc is unready before allocation, so Capacitor is the sole pre-allocation candidate and receives the full 2 U. It now holds 3/4. With all parts already mounted and accessible, the player opens the fully paused journal, previews the compatible change, disconnects Sensor from Projector and connects Capacitor manual release→Lens→Projector. No enemy, oxygen, readiness or heat state advances during that link edit. The player then closes the journal and selects a valid displayed Projector target. A pickup, physical mount or removal would still take live-world time.
-
**Action 3:** Lens accepts the 2 U first receiver check, so release commits, Capacitor falls to 1/4 and Lens converts the charge to heat. Before Projector resolves, its target becomes invalid behind hard cover. Projector refuses. The heat packet dissipates there; the 2 U and paid rewire are not refunded. The case determines failure without asserting heat damage or build strength.
+
**Action 3:** Lens accepts the 2 U first receiver check, so release commits, Capacitor falls to 1/4 and Lens converts the charge to heat. Before Projector resolves, its target becomes invalid behind hard cover. Projector refuses. The heat packet dissipates there; the 2 U is not refunded and the edited links remain as shown. The case determines failure without asserting heat damage or build strength.
### C. Counterwall partial, full, saturation and pre-release refusal
@@ 223,33 228,33 @@
| Owning source | Finite alignment after acceptance |
|---|---|
-
| **Equipment Catalogue** | Replace Fork's open split/threshold and Capacitor's open storage/overflow language with the fixed output order, 4 U hold, vent overflow and 2 U release. Preserve all twelve parts, bare-trigger copying and once-per-wave behavior. |
+
| **Equipment Catalogue** | Replace Fork's open split/threshold and Capacitor's open storage/overflow language with the fixed output order, 4 U hold, vent overflow and 2 U release. Preserve all twelve parts and bare-trigger copying. A later catalogue pass may give a named part or temporary effect an echo allowance; descendants cannot refill the event that created them. |
| **Survival And Loadout** | Reference the proposed O/C sheet, reserve mark and transfer arithmetic; keep incremental conservation, free ordinary refill and non-restoration of prepared surplus. |
-
| **Equipment Acquisition And Rig Growth** | Fill navigation-coupler/thermal-core at 2 C each, retain bridge/regulator at 2 C, and align reclaim/rig examples without changing twelve sources or reversible ship states. |
-
| **Combat And Enemy Roster** | Replace only the multiple-ordinary-actuator gap with the one-independent-launch envelope. Keep target/readiness, ordinary/manual distinction, causal waves, roster and encounter counts. |
+
| **Equipment Acquisition And Rig Growth** | Fill navigation-coupler/thermal-core at 2 C each, retain bridge/regulator at 2 C, and align reclaim/rig examples to multi-output legality, paused link editing and temporary-upgrade reset without changing twelve sources or reversible ship states. |
+
| **Combat And Enemy Roster** | Align the multiple-ordinary-actuator gap to independent per-actuator target/readiness plus visible shared power and heat. Keep ordinary/manual distinction, causal waves, roster and encounter counts; combat owns crest arrival, pressure and break presentation. |
| **Home And Colony Loop** | Owns commissioning, later solo operation, one lent part and completed products, and links here for collar and bench control details. |
| **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. |
-
| **Build Rules** | Adopt the same envelope and numeric split/storage example without turning it into an exhaustive port/duplicate grammar. Keep field edits in world time and descendant once-per-wave resolution. |
+
| **Build Rules** | Adopt the same multi-output envelope, paused mounted-link editing, finite echo conservation and numeric split/storage example without turning it into an exhaustive port/duplicate grammar. Keep physical pickup, mounting and removal in live world time. |
| **Connecting The Station** | Explains the discovery direction and leaves the joining mechanism open. The R26/R33 cards here remain part of the conditional technical candidate, not required rules for that entry page. |
-
| **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. |
+
| **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. A rig proposal also shows per-actuator target/readiness, total visible power demand, heat and remaining echoes where applicable. Presentation/default/accessibility remain Information34-owned. |
| **Save / global04 continuity** | Store exact canister O, Capacitor U, Fork/object location, rig links, fixture stage/commits, R26 mode and completed evidence. Apply property-first death and stable room/object identity. Retained charge across death/return remains with that owner and is not decided here. |
-
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.
+
The mechanical handoff is therefore finite: each ordinary launch source and actuator identity, each actuator's selected target/readiness commit, one causal-sequence identity, remaining echo count and heat where a return effect uses them, 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.
## Decision record, costs and open work
-
**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.
+
**Candidate choice.** Allow several independent ordinary launch paths, each with its own target and readiness, bounded by visible rig space, carrying, power and heat. Use finite echo conservation for named return effects, conservative fixed-order Fork division, hold-and-vent Capacitor storage, fixed 2 U manual release and the one provisional opening quantity sheet. This keeps Sensor/Stride coexistence, manual specials and derived cascades 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.
+
**Accepted cost.** Multi-output rigs require the interface and encounter language to expose several targets, readiness states, total power and heat without hiding causality. Echoing effects add return-state pressure even with a finite counter. 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.
+
**Smaller supported variant.** Give the opening backplane a visible supply that powers one direct Sensor→Projector or Stride→Projector path, while keeping the same general legality and later allowing additional automatic outputs through found supply. Keep the quantity sheet and fixed storage policy, and omit Fork branching from opening ordinary fire. Counterwall, Cycler and paused-link descendants remain. This loses the opening's Sensor→Fork→Projector+Barrier control trade but does not impose a universal one-launch rule or 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.
+
**Open rather than invented.** Duplicate quantity/stacking, exact supply/draw/heat/echo numbers, 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. Pending owner questions are unanswered.
-
**Later discrimination.** Only a later owner-authorized implementation and observation could test whether target ownership, lost shares, storage, fixture recovery, reserve marking and packing choices are comprehensible or enjoyable; whether the numbers create useful pressure; whether four- and six-A builds remain viable; or whether duplicate ordinary launches are worth their complexity. This paper arithmetic demonstrates conservation and determinacy only.
+
**Later discrimination.** Only a later owner-authorized implementation and observation could test whether multiple target/readiness displays, power/heat, echoes, lost shares, storage, fixture recovery, reserve marking and packing choices are comprehensible or enjoyable; whether the numbers create useful pressure; or whether multi-output rigs dominate focused chains. This paper arithmetic demonstrates conservation and determinacy only.
## Author self-check and finite count
-
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.
+
The article contains the bounded controller correction, 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 external 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. Multiple Sensor/Stride launch paths are legal under per-actuator target/readiness and visible shared power/heat; a finite echo budget permits named returns while descendants cannot refill the same event. 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.
Content counts remain **12 catalogue parts, four opening starters, eight later part sources, four ship assemblies, 24 modules/40 station rooms, 10 encounters including two setpieces, 13 major mechanisms and five home projects**. This article adds zero portable parts, resources, rooms, encounters, major mechanisms, survivors, story scenes or unseen destinations. It performs no code, executable/modelled simulation, asset work, playtest or validation and answers none of the five owner questions.
