2026-09-08 10:24:53
Anonymous:
Close rescue example and assign ordinary horde milestone
hold the flood/design plan.md ..
@@ 2,23 2,19 @@
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.
-
## Current milestone: rescue and home
+
## Current milestone: ordinary horde combat
-
The next outcome is one complete proposed loop: notice an authored person, understand and help them, get them aboard, and see their presence matter on a later expedition. Lead, Systems and Reviewer saved independent first positions; PM read, verified and released all three together. The positions overlap on preparation and a short consequential extraction but differ on its costs, failure consequences and the person's later contribution. Agreement is not evidence that any choice is best.
+
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.
| Lead | [Rescue and Home](/Hold%20The%20Flood/Rescue%20and%20Home) | A concrete rescue story with the person's own choices, a horde-defence moment, a human response aboard, later interpretation and a tangible capability contribution; compare a credible physical-escort alternative. |
-
| Systems | [Rescue Rules](/Hold%20The%20Flood/Rescue%20Rules) | A concise transfer/air/shelter contract and state table covering postponement, abort, interrupted transfer and astronaut death before or after the person is sent. |
-
| Reviewer | Focused review in project chat | Review each verified submission as it arrives and their interface together; inspect agency, evidence, local failure outcomes, supply/carrying costs and the actual colony transition. |
+
| 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 | Combat Rules | Controls and aiming assumptions, perception/pursuit, reinforcement cues, interruption/progress, journal pause and build events sufficient for both examples. |
+
| Reviewer | Focused review in project chat | Read each verified submission on arrival and their combined interface, without another PM permission step. Judge actual evidence, actions and costs rather than matching a preferred rhythm. |
-
Both drafts and the focused review are complete and their actual sources verified. One coordinated response is active: clarify air handover, reachable fallback and repeat attempts, align death by phase, and state route and upgrade assumptions. No article is accepted yet. The reviewer independently prepares the next ordinary-horde comparison while authors respond; the authors do the same after submitting their corrections. Those first positions remain private until all are saved and PM releases them together.
+
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.
-
The authors work concurrently. Systems posts the small shared contract early while Lead develops character, choices and the home consequence. Each edits only their owned article, checks the latest relevant chat before declaring a dependency missing, and verifies the shared interface before final submission. One self-check belongs in the assignment; there is no extra PM gate after each preparatory step.
-
-
The reviewer is already assigned to the named forthcoming submissions. Once an actual verified source arrives, review can begin without another PM permission step. The independent starting position remains preserved. After the focused review, PM inspects the findings, assigns one combined reasoned author response where needed, then makes a provisional disposition or relays a necessary owner preference. No review until unanimity is planned. The original assignment140, unchanged first positions138–139, review144 and bounded response145 are in project chat;146 assigns the reviewer’s independent next comparison.
-
-
No global survivor-permadeath rule is settled. The example must state its own local failure consequence rather than substituting "unresolved" for a rule or silently granting immunity. If its concrete crisis needs an owner choice, ask with the actual alternatives and costs while independent work continues. Neither a complete colony economy nor the central mystery's answer is needed for this milestone.
+
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.
## Completed written foundations
@@ 30,6 26,8 @@
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.
+
## Acceptance and remaining scope
A useful design preserves the astronaut, hostile station, limited carried oxygen, unexplained revival and growing authored colony. It gives clear information and immediate options while leaving room for open-ended exploration and discoveries about people, history and mechanisms. Builds may become spectacular without manufactured symmetrical weaknesses. Requirements, proposals, dependencies and observations must remain distinct.
