2026-09-08 10:39:07
Anonymous:
Response to review 161 and PM 162/165: owner automatic-fire decision integrated, journal capture boundary corrected, clearance scope bounded, condition cost stated, alcove claim narrowed, frequency lever named through placement
hold the flood/horde encounters.md ..
@@ 10,15 10,21 @@
**Objective.** Get to the door at the far end.
-
**What the player sees before committing.** From the junction mouth the whole run is visible and lit. The crowd's spread is readable: thick across the middle, thinner along the left wall. One alcove halfway down has nothing in it, and nothing goes near it.
+
**What the player sees before committing.** From the junction mouth the whole run is visible and lit. The crowd's spread is readable: thick across the middle, thinner along the left wall. And halfway down there is an alcove that ordinary enemies path around — none enters it, and none is standing in it.
-
**Decisions.** Push the middle, where the crowd is densest and a cascade has the most to work with. Move along the thin wall, trading damage for exposure and timing. Or back out and take a branch route, which costs oxygen and time and is a legitimate answer, not a failure.
+
That is the whole of what can be observed, and it is observable from the mouth without fighting anything. Why they avoid it is not established, and the player has no grounds to conclude it is safe for *them* — an anomaly worth recording and testing, not a proven refuge.
-
**With the Relay Cascade Array.** Density is the Array's best case: aimed into the packed middle, the chain branches through the crowd and the run empties. Per the combat contract, that is simply a win — the area stays clear for this expedition, and the player has bought the direct route, quiet working time at the door and the oxygen margin they would otherwise have spent going around. No replacement wave arrives and no compensating elite appears. A build that trivialises an ordinary crowd is the point of having built it.
+
**Decisions.** Push the middle, where the crowd is densest and a cascade has most to work with. Move along the thin wall, trading damage for exposure and timing. Or back out and take a branch route, which costs oxygen and time and is a legitimate answer, not a failure. With ordinary fire mostly automatic, these are positioning and timing choices: the run is crossed by deciding where to be and when to spend a special, not by landing individual shots.
-
**With the Cargo-Cycler Rig.** The Cycler does not clear the run and does not need to. A shove compresses the middle group off the left wall, and a fragment burst opens a lane long enough to cross. It costs colony-bound salvage rather than a permanent module, and it leaves the run occupied behind the player — which matters on the way back.
+
**With the Relay Cascade Array.** Ordinary fire is mostly automatic and special abilities are triggered by hand (owner requirement), so the player's decisions here are where to stand, which way to press, and when to spend a special — not whether each shot connects. Density is the Array's best case: moving into the packed middle puts its automatic output where the chain has most to branch through, and the run empties. That is simply a win: the run's crowd is gone for this expedition, and the player has bought the direct route and the oxygen they would have spent going around. No replacement wave arrives and no compensating elite appears. A build that trivialises an ordinary crowd is the point of having built it.
-
**Why fight rather than pass.** Two reasons that are not a toll. First, this is where an expressive rig becomes visible: the crowd is the canvas, and clearing it is the payoff for the parts committed to that build. Second, the empty alcove is information. Something about it keeps ordinary enemies out, and that is a fact the player can record and use without enemy behaviour becoming the subject of experimentation.
+
What it does not buy is a quiet door. The run up to the door vestibule is this encounter's boundary; clearing it does not defeat the caller beyond, or consume groups in connected spaces. Nor does "clear" mean sealed: something living outside can later walk in along a real route, always cued by sight, sound or door movement, never behind the player.
+
+
**With the Cargo-Cycler Rig.** The Cycler does not clear the run and does not need to. A shove displaces the middle group off the left wall — displacement, not a wall, since nothing here builds a lasting barrier — and a fragment burst opens a lane long enough to cross. The run stays occupied behind the player, which matters on the way back.
+
+
**The two rigs spend differently, and neither is simply cheaper.** The Array's modules occupy carrying space permanently but are not consumed per use, so its clearing costs capacity decided at the ship. The Cycler keeps capacity flexible but spends chosen salvage each time, so its lane costs colony-bound material during the trip. Which is dearer depends on what is scarce that expedition.
+
+
**Why fight rather than pass.** One honest reason, not two: this is where an expressive rig becomes visible and enjoyable, and clearing the run is the payoff for the parts committed to it. Fighting also buys the direct route. It does *not* buy the alcove — that anomaly is visible to anyone who looks, and a player who slips past sees it just as well. Enemy behaviour is legitimate information; it is not a reward for combat, and manipulating it is not the experiment.
**Withdrawal.** Backing out to the junction is always available. Enemies search the last place they perceived and settle, and the player has spent time and oxygen, not progress.
@@ 30,19 36,23 @@
**What the player sees before committing.** The door's state and its remaining bolts are readable at a glance, as are the two approaches to the panel and which one has cover. So is the reason this will be harder than it looks: cutting and cycling are loud, and the run's occupants investigate loud things.
-
**The pressure is caused, not scheduled.** Nothing here escalates because the player is doing something interesting. The door grinds, and grinding is a physical event ordinary enemies come to look at. Quiet looking, moving, framing a record and reading the journal draw nothing. This example also contains one visible caller — an ordinary enemy that, allowed to finish its warning, brings a group from the adjacent area. Killing it first is a real targeting decision with a readable consequence; the run in encounter one has no such source and does not escalate.
+
**The pressure is caused, not scheduled.** Nothing escalates because the player is doing something interesting. The door grinds, and grinding is a physical event ordinary enemies come to look at. This example also holds one caller — an ordinary enemy that, allowed to finish its warning, brings a group from the adjacent space. Before committing to the first bolt the player can see or hear it, recognise its warning behaviour, and see the connected entrance it would summon from. Dealing with it first is a real priority decision with a readable consequence. Ordinary fire takes the nearest valid target, so reaching the caller with it means positioning until nothing else qualifies first — which may mean clearing what stands between. The alternative is spending a manual special to stop the warning in time. That is the choice: rearrange yourself, or spend something. The run in encounter one has no such source.
+
+
**Decisions, and what they cost.** Clear the approach and the caller first, then work undisturbed, spending build resources up front. Work in bursts between arrivals, using a Cycler shove to displace what arrives and buy stages — displacement, not a barrier. Or take what has been done and leave.
-
**Decisions.** Clear the approach first and then work in peace, spending the build's resources up front. Work in bursts between arrivals, using a Cycler shove to block the narrow approach and buy stages. Or accept what has been done and leave.
+
The middle option has a price that lasts: taking hits spends condition, and lost condition does not come back in the field. It narrows the margin before a damage death for the rest of that expedition, including the walk home. So working under fire is not free just because damage cannot cancel a stage — it borrows against every later margin on the trip.
-
**Interruption, stated exactly.** The work has named visible stages — each bolt, then each cycle of the door. Leaving before the current stage completes loses that stage and the time and oxygen already spent on it. Completed stages persist. Damage alone does not cancel the work; an enemy stops it only by a readable physical result, such as forcing the astronaut off the control. So withdrawal has a real opportunity cost without permanent loss: nothing resets, the bolts already cut stay cut, and the trip that ends here is one that bought fewer stages than it hoped.
+
**Interruption, stated exactly.** The work has named visible stages — each bolt, then each cycle of the door. Leaving before the current stage completes loses that stage and the time and oxygen already spent on it. Completed stages are checkpoints and do not roll back. Damage alone does not cancel the work; an enemy stops it only by a readable physical result, such as forcing the astronaut off the control. So withdrawal has a real opportunity cost without permanent loss: the trip that ends here bought fewer stages than it hoped, and the bolts already cut stay cut.
+
+
Backing out is a route decision, not a guarantee. The way to the junction can be held by something, and choosing to leave is not the same as being able to.
**With the Array.** Clearing the approach outright means the door is finished without interruption. That success is not clawed back.
**With the Cycler.** Blocking the approach is cheaper than clearing it and leaves the player working with something moving nearby — a different texture, not a worse outcome.
-
**Room to think.** Between arrivals there is quiet, and the journal pauses everything, so the painted mark on this door frame can be read and recorded without the encounter punishing the reading. Pressure applies to *doing*, never to looking or thinking.
+
**Room to think, stated precisely.** The journal pauses enemies, oxygen and action progress, so *reading* stored records and the already-visible frozen view is free. Capturing is not: framing and committing a record of the painted mark on this door frame is a world-time action, and physically studying it spends oxygen while the run's occupants keep moving. Looking raises no attention by itself, but it is not outside time. Thinking over what is already held is protected; getting new evidence into the journal is priced.
-
**On return.** The door's cut bolts and completed cycles are exactly as they were left. The population around it is not.
+
**On return.** Cut bolts and completed cycles are deliberate physical changes and persist across expeditions; the population around them does not. What can still block progress is a genuine new change — the door's feed losing power, a bolt re-jammed since. That prevents the *next* stage without rolling back a completed one, and must be an authored change the player can read, never a quiet reset of earned work.
## Comparison
@@ 59,14 69,18 @@
**The route crowd should be the ordinary case; the contested mechanism should be occasional.**
-
This is a change from my first position, which favoured pressure-while-acting as the common rhythm, and the reason is that I had not separated *which matters more* from *which should happen more often*. Contested-action encounters are the stronger of the two — they put the price on the thing the player actually came to do — but their weakness scales directly with frequency. If every world-time action is harassed, the causal pressure starts reading as a trigger attached to interesting objects, which is the failure I named as this structure's own risk. Rare, it lands. Constant, it becomes suspicious.
+
Contested-action encounters are the stronger of the two — they put the price on the thing the player actually came to do — but their weakness scales with frequency. If every world-time action is harassed, causal pressure starts reading as a trigger attached to interesting objects. Rare, it lands; constant, it becomes suspicious.
+
+
Route crowds carry the ordinary rhythm better because they ask a question with several legitimate answers — fight, slip past, go round — none of which is a failure state.
+
+
**How the preference is applied, since frequency is not a dial.** Pressure is caused, not scheduled, so "occasional" is not set directly — it is an outcome of placement, which is where the choice actually lives: how many of an area's world-time actions are loud ones like bolt-cutting rather than quiet ones; whether a mechanism sits in a connected area holding population or off a dead run where grinding reaches nobody; whether an area has a caller or alarm source at all; and how entrances connect, since a cued approach from a known direction reads differently from one the player cannot anticipate. Choosing this rhythm means authoring those causes deliberately. No frequency figures are proposed.
-
Route crowds carry the ordinary rhythm better because they ask a question the player can answer in several legitimate ways — fight, slip past, go round — and because being pushed onto an unplanned route is one of the cheapest ways this design produces discovery.
+
**What the branch offers, since the comparison leans on it.** Here the branch that avoids the run loops behind the alcove and reaches it from the far side, so a player who declines the crossing meets the same anomaly from an angle the run never shows. That is one worked example, not evidence that detours generally pay: the claim that unplanned routes produce discovery is a prediction resting on placement doing that work.
-
**Strongest alternative.** Make contested actions the default. It gives a tighter and more consistent rhythm, keeps combat permanently tied to what the player is trying to achieve, and never lets fighting drift into scenery. If the trigger-feel worry turns out to be unfounded, this is the better arrangement, and it is what my own first position argued for.
+
**Strongest alternative.** Make contested actions the default. It gives a tighter, more consistent rhythm, keeps combat permanently tied to what the player is trying to achieve, and never lets fighting drift into scenery. If the trigger-feel worry proves unfounded, it is the better arrangement.
**Accepted costs.** Two encounter kinds at different frequencies risk reading as two disconnected modes, and a player may meet contested work rarely enough not to get good at it. The alcove-style oddity depends on authored placement, so it is not free. And the claim that a powerful build needs no compensating penalty because oxygen and capacity already constrain the player is a proposal, not a demonstrated balance: those limits may or may not prove sufficient, and only later authorised observation could say.
## Unresolved
-
How often "occasional" is; whether readable anomalies like the alcove stay interesting once their cause is known; whether route crowds without escalation sources remain tense; and the enemy roster, none of which is proposed here.
+
Why the alcove is avoided, and whether such anomalies stay interesting once explained; whether route crowds without escalation sources remain tense; and the enemy roster, not proposed here. Ordinary target selection, optional aim assistance and equipment exceptions remain to be designed within the owner's firing decision, and [Combat Rules](/Hold%20The%20Flood/Combat%20Rules) owns that contract along with condition and its recovery, on which the door decision above depends.
