2026-09-08 10:53:31
Anonymous:
Close combat written milestone and launch discovery chain and help comparison
hold the flood/design plan.md ..
@@ 2,19 2,21 @@
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: ordinary horde combat
+
## Current milestone: a discovery that earns its reinterpretation
-
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.
+
Across three visits, one local discovery should change the meaning of an earlier observation and give the player a reasoned new decision. All three independent first positions were saved, read and hash-verified before their joint release in project chat175–177. Similar preferences do not settle the comparison: the concrete evidence and the value of survivor help need a stronger account.
| Lead | [Horde Encounters](/Hold%20The%20Flood/Horde%20Encounters) | 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](/Hold%20The%20Flood/Combat%20Rules) | 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. |
+
| Lead | [Discovery Chain](/Hold%20The%20Flood/Discovery%20Chain) | One language-related local discovery with precise observations, plausible rival readings, discriminating evidence, an earned understanding, a changed choice and a worked missed-clue or reversed-order path. |
+
| Systems | [Clues and Help](/Hold%20The%20Flood/Clues%20and%20Help) | Evidence and journal contract, knowledge versus unlocks, survivor help/access, persistent records and a concrete inventory of the chain's authored content. |
+
| Reviewer | Focused review in project chat | Read each verified submission on arrival and their combined interface without a further PM gate. Examine the actual evidence, meaningful understanding, credible alternative and honest scope claims. |
-
Both combat articles and the focused review161 are complete, with actual sources verified. A single coordinated response162 is active: clarify alert/clearance scope, record exposure, completed-work persistence, condition/recovery and evidence/cost claims. The reviewer independently prepares a discovery-chain comparison under163 while authors revise; authors prepare their own after response submission. Those new positions remain private until all are saved and jointly released. Systems supplied the shared contract157 before Lead’s draft. No combat proposal is accepted yet. 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 original assignment155 and unchanged positions152–154 remain in project chat;162 assigns the coordinated response and163 the reviewer’s independent next comparison. The owner selected mostly automatic firing with manually activated special abilities. The requirement is recorded in the updated brief and relay165; authors integrate it in response162. Targeting, bindings and particular equipment exceptions remain design proposals.
+
Assignment178 gives each author a complete parallel outcome and preauthorises the named review after the already-saved independent checkpoint. Systems posts the proposed shared interface early. Authors read the other's available source, verify their own publication, report exact dependencies and stop article edits. PM reviews the actual output and critique, coordinates one focused response if needed, and makes a provisional disposition. Unanimity is not a completion requirement.
-
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.
+
A symbol's location or a working mechanism does not by itself prove a translation. Later evidence must distinguish a real rival reading, while residual ambiguity can remain. The chain should earn some positive understanding, not only undermine a first guess. Limited truthful survivor translation can preserve agency; compulsory rescue gates, deliberate fallibility and cryptic hints are properties of particular proposals, not requirements. Personal notes are welcome, and the journal pauses the game as the owner requested.
+
+
The local language use may be proposed, but no alphabet, complete language system or central revival/station/escape answer is assigned. Service-family notation is not one of the two alien languages required by the brief; one example cannot fulfil the complete language requirement. There is no implementation, simulation, playtest, numeric balancing, campaign or asset authorization.
## Completed written foundations
@@ 28,6 30,8 @@
[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.
+
[Horde Encounters](/Hold%20The%20Flood/Horde%20Encounters) and [Combat Rules](/Hold%20The%20Flood/Combat%20Rules) are provisionally integrated after focused review, response and final consistency edits, disposition174. Route crowds and selectively contested work are the working rhythm; a cleared route does not erase a door caller or prevent later cued movement. Completed work persists and withdrawal depends on actual occupants and pursuit. The owner's mostly automatic ordinary fire and manual specials are required; nearest-valid targeting and readiness are proposed details. The observed alcove anomaly is available to avoidance too. Carrying, salvage and condition costs are explicit, with no guaranteed escape or established cheapness claim. Lead owns the encounters and Systems the rules. No broad second combat review is pending; fun, frequency, balance and control readability remain unvalidated.
+
## 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.
