Commit 008a57

2026-09-15 12:53:25 Anonymous: Record completed combat package and next expedition case; forecast F2.5
hold the flood/design plan.md ..
@@ 11,7 11,7 @@
- [Build Comparison](/Hold%20The%20Flood/Build%20Comparison): three builds with different ordinary play, growth, manual specials, physical costs and discoveries using their parts in the station.
- [Expedition Proposal](/Hold%20The%20Flood/Expedition%20Proposal): three successive outings with fresh growth, meaningful hordes, changing objectives and permanent progress.
- Both proposals completed an independent critique, one response per author and PM checks. They are ready for owner reaction; the new build exceptions still need detailed reconciliation. Systems has submitted a concrete growth rhythm and renewed route through existing rooms and is making its one response to independent review. In parallel, the [hospital-story](/Hold%20The%20Flood/Hospital%20Story%20Directions) and [survival/loadout](/Hold%20The%20Flood/Survival%20And%20Loadout) proposals completed their review and response. They are ready for owner reaction; the alternative story explanations remain revisable. Combat design and its supporting pages continue while the owner chooses which build direction to deepen first. Actual task states and delivery estimates are on [Progress](/Hold%20The%20Flood/Progress).
+ Both proposals completed an independent critique, one response per author and PM checks. They are ready for owner reaction; the new build exceptions still need detailed reconciliation. The [combat growth and renewed route](/Hold%20The%20Flood/Combat%20Rules) also completed review and integration into the room, encounter and survival references. The next concrete case is fresh combat after all four enemy sources on that route are permanently sealed: the player must keep the benefit of the seals and the open shortcut. In parallel, the [hospital-story](/Hold%20The%20Flood/Hospital%20Story%20Directions) and [survival/loadout](/Hold%20The%20Flood/Survival%20And%20Loadout) proposals completed their review and response. They are ready for owner reaction; the alternative story explanations remain revisable. Combat design and its supporting pages continue while the owner chooses which build direction to deepen first. Actual task states and delivery estimates are on [Progress](/Hold%20The%20Flood/Progress).
## What makes a proposal ready
@@ 23,7 23,7 @@
## After the core proposal
- The selected renewal and regular-growth rules are aligned in the main combat, persistence, equipment and encounter references. Next, map that growth onto real routes and reconcile the selected build directions with their detailed mechanics. Develop the hospital and alien setting, characters, short rescues, language discoveries and story consequences through concrete scenes alongside that combat work. Present the owner with consequential creative alternatives; handle routine consistency and readability within the team.
+ The selected renewal and regular-growth rules are aligned in the main combat, persistence, equipment and encounter references. One real route now shows that growth with open sources. Next, resolve the fully sealed version and reconcile the selected build directions with their detailed mechanics. Develop the hospital and alien setting, characters, short rescues, language discoveries and story consequences through concrete scenes alongside that combat work. Present the owner with consequential creative alternatives; handle routine consistency and readability within the team.
Use [Open Decisions](/Hold%20The%20Flood/Open%20Decisions) as the issue index. Its recommendations remain proposals, and its categories overlap. The team should not wait for fourteen separate owner answers or assume that every criticized rule needs wholesale replacement.
@@ 31,8 31,8 @@
## Open questions
- - Which precise growth rhythm, reward presentation and milestone conditions best support the selected direction?
- - How should permanent changes alter fresh crowd placement without creating long empty approaches?
+ - The current regular-growth rhythm and milestone conditions are a reversible proposal. How well will they sustain excitement across other expeditions?
+ - After all four enemy sources on the sample route are permanently sealed, where does a worthwhile fresh horde fit, and what advantage does the player retain?
- Which story and rescue consequences should be offered to the owner next?
- What does completing the station connection do, and what content scope can support the intended journey?
- The rules and numbers are proposals; practical testing awaits the owner's development-phase authorization.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9