The team is designing a discovery-first survivorlike under the [Owner Brief](/Hold%20The%20Flood/Brief), with expressive builds, meaningful hordes and an authored colony. The work below is design only. Written comparisons establish a proposal and its dependencies; they do not demonstrate fun, readability, balance, production feasibility or campaign duration.

The next outcome is a concrete pair of ordinary encounters and their proposed combat rules. All three independent first positions were saved, read, hash-verified and jointly released. They disagree on whether route pressure or pressure during investigation should be common. Their examples and costs, rather than a majority preference, guide this comparison.

| Writer | Owned forthcoming output | Required outcome |

| Lead | Horde Encounters | A route crowd and an investigation/action encounter: readable information, player choices, powerful-build success, withdrawal and a changed return. Compare the common rhythm with its strongest alternative. |

Systems supplies the small shared contract early while Lead writes player decisions and setting. The authors cross-check actual available sources before final submission and stop article edits for review. The review has one bounded response and PM disposition; no review until unanimity is planned. The current assignment is155 and the unchanged original positions are152–154 in project chat.

No numerical balancing, implementation, simulation, playtest, art, complete enemy roster or central mystery answer is assigned. A strong build can win decisively and avoidance can be legitimate. The comparison must give fighting its own value while preserving discovery by thought, quiet observation and the owner's paused journal.

- [Expedition Proposal](/Hold%20The%20Flood/Expedition%20Proposal) and [Build Comparison](/Hold%20The%20Flood/Build%20Comparison): a provisional sortie with observed glyph evidence, contrasting equipment/cargo builds, carrying choices and a survivor interpreting a player-shown clue. The particular notebook use and survivor contribution do not prohibit other uses or cast roles. The comparison's inspection and activation wording now matches the later build rules.

The foundations milestone closed after review125, coordinated responses and final PM consistency edits, disposition137. Article ownership is Lead for Expedition, Exploration and Death; Systems for Build Comparison, Build Rules and Oxygen. No further broad foundations review is pending. Their working proposals can be reopened for a concrete contradiction, owner preference or later authorized evidence.

[Rescue and Home](/Hold%20The%20Flood/Rescue%20and%20Home) and [Rescue Rules](/Hold%20The%20Flood/Rescue%20Rules) are provisionally integrated after focused review and response, disposition158. The Dorn example combines traces, an expressed route preference, cooperative crossings and a home contribution. Air handover, current-refuge death, a finite route and a resealable final abort vestibule are explicit. Continuous escort remains credible; no global survivor-loss rule or proven emotional impact follows. Ownership is Lead for the story and Systems for the rules.