You leave home with a modest rig, fight through a growing horde, discover a powerful interaction between your equipment and the station, and return with something that changes the next expedition. That sequence must be exciting on the third trip as well as the first.

The owner chose fresh hordes each expedition and regular combat growth with larger transformations. Permanent changes and physically carried property remain, while temporary power resets on returning home. The [Owner Brief](/Hold%20The%20Flood/Brief) records the requirements.

The main reading path now begins with [The Game](/Hold%20The%20Flood/The%20Game), follows [three expeditions](/Hold%20The%20Flood/Expedition%20Proposal), returns to [the people aboard](/Hold%20The%20Flood/Coming%20Home), and opens into [discovery in the changing station](/Hold%20The%20Flood/Connecting%20The%20Station). [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds) explains the current examples; [Build Comparison](/Hold%20The%20Flood/Build%20Comparison) presents alternative controls and payoffs for owner reaction.

Five proposal packages completed review and response today: builds/expeditions, hospital story/survival, regular growth on a renewed route, a second route state after permanent source seals, and the six-page reading path. [Combat Rules](/Hold%20The%20Flood/Combat%20Rules) and the room/encounter references describe the two concrete route states. They preserve completed work while giving fresh opposition a physical route. Other seal combinations and shifted layouts remain design work.

The new Ricochet and Gravity mechanisms remain proposed replacements for parts of the detailed build rules. The [hospital-story alternatives](/Hold%20The%20Flood/Hospital%20Story%20Directions) remain revisable. Completed review does not select them for the owner or establish fun, balance or duration.

The moving lamp promises a strong sequence: pursue an apparent constellation, fight alongside its carriage, earn a spectacular build release, and discover a bridge that changes the next trip. Systems is placing that sequence in the actual station, with one proposed location, visible sources, growth before the climax, a usable withdrawal and evidence that supports the discovery. Added geometry and content costs must be explicit.

One focused critique and one author response belong to this bounded outcome. The current reader pages remain stable while the separate proposal is prepared. PM is also checking the outside-edit bundle for lost meaning; this preservation work does not reopen every accepted design debate. States and estimates are on [Progress](/Hold%20The%20Flood/Progress).

The reader can picture what the player wants, sees and does. Pressure develops through meaningful horde combat. A growth choice changes the next movement decision; a build breakthrough creates a visible payoff; quiet lets a discovery change an understanding or future action.

Builds differ in behavior, attention and cost. Their strongest results should feel constructed and discovered. Practical limits should support interesting choices without automatically suppressing powerful combinations. Each substantial scene identifies a plausible way its intended pleasure could fail.

Readable prose leads with an example and explains necessary terms where they arise. Detailed references support the explanation. Discussion history and execution records stay outside game descriptions. Written consistency helps us design; later evidence is still needed to establish the experience.

- Extend renewal and regular growth across worthwhile expeditions with different goals and crowd patterns.

Use [Open Decisions](/Hold%20The%20Flood/Open%20Decisions) as an overlapping issue index. Its recommendations remain proposals; the team handles routine consistency and brings consequential creative alternatives to the owner. Development, simulations, playtests and game assets await separate authorization.