Blame
|
1 | # Hold The Horde — Design Plan |
||||||
| 2 | ||||||||
|
3 | 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. |
||||||
|
4 | |||||||
|
5 | ## Current milestone: integrate the owner decisions |
||||||
| 6 | ||||||||
| 7 | The owner accepted connected equipment combinations, shared oxygen/equipment/loot capacity, practical clue-based exploration and the route/work horde rhythm. Equipment loans at home are tentative. The owner rejected death caches: carried equipment and new loot return aboard on death. Persistent-station and cooperative-rescue proposals await clearer explanation, not inferred approval. The [Owner Brief](/Hold%20The%20Flood/Brief) records these decisions. |
|||||||
| 8 | ||||||||
| 9 | PM249 assigns one bounded integration across each author's owned pages. Lead rewrites Death and Persistence and resolves direct contradictions in its dependent scenes; Systems finishes its active language revision then resolves the corresponding equipment, survival and mystery contracts. No replacement punishment, repeated preference question or broad rewrite is assigned. Old cache statements are superseded now and are being removed. |
|||||||
| 10 | ||||||||
| 11 | ## Parallel milestone: a concrete language expedition |
|||||||
|
12 | |||||||
|
13 | All independent language originals were saved before peer new conclusions, verified and released233–235. Assignment241 gives Lead sole ownership of [Language Expedition](/Hold%20The%20Flood/Language%20Expedition) and Systems sole ownership of [Language and Journal](/Hold%20The%20Flood/Language%20and%20Journal). These forthcoming articles will connect two distinct alien languages, observable clues, competing interpretations, useful assistance and a consequential player choice with the actual journal interactions. Feedback and help remain provisional; neither automatic certainty nor withheld confirmation is inherently superior. The owner-required journal pause remains fixed. |
||||||
|
14 | |||||||
|
15 | Reviewer retains [Language Design Evidence](/Hold%20The%20Flood/Language%20Design%20Evidence), with a focused source correction assigned before a preauthorised review of the two submitted language articles. Heaven's Vault permits narrative progress amid uncertainty but later context can reveal wrong guesses; Chants of Sennaar has developer-reported playtesting, not a public validation dataset for this project. Fixed geography does not rule out adaptive content selection, and confirmation/help need not eliminate interpretation. The exact evidence corrections and review completion boundaries are in241. The original Reviewer host has recovered under the same identity and automatically received241. It is correcting the evidence and will review the actual submitted language revisions. |
||||||
|
16 | |||||||
|
17 | Both initial language articles are submitted and actually read. PM246 assigns bounded corrections to the clue-to-route inference, substantive visitor-language example, interpretation of survivor labels, and the distinction between completed and inconclusive local tests. Systems already replaced freeform grading with separately selected outcome links. The original Reviewer correction/review is active after verified host recovery. Authors write substantial parallel outcomes with an early shared example and final actual-source coherence check. No full conlang, artwork, implementation, prototype, simulation or playtest is assigned. PM verifies sources and accepts integration; author submission or agreement does not establish fun, accessibility, balance or content feasibility. |
||||||
|
18 | |||||||
|
19 | ## Parallel work: final mystery comparison |
||||||
|
20 | |||||||
|
21 | [Mystery Directions](/Hold%20The%20Flood/Mystery%20Directions) and [Mystery Consequences](/Hold%20The%20Flood/Mystery%20Consequences) have completed one review230 and coordinated response232, with final submissions238/240 actually read. PM completed narrow final integration after ownership transfer241 and returned ownership to Lead/Systems in the comparison disposition. The three story candidates completed comparison preparation247. Their inventory-return explanations now need the narrow owner-decision update249 before being pitched as the current version. No central direction is adopted and no second broad review is pending. |
||||||
|
22 | |||||||
|
23 | The final comparison distinguishes departure permission from service cancellation, uses an individual casualty tag and arranged failure for the Unit, adds a quarantine-control cause for the Registry, and gives the Clinic a concrete programme intervention with coherent evidence. These are explicit candidate choices and costs, not owner commitments. Ordinary revival continues while the player pursues the deeper path; final departure ends it. Causal eligibility does not adopt global survivor mortality. The owner will receive concrete story alternatives before commitment, not an abstract forced choice. |
||||||
|
24 | |||||||
| 25 | [Coming Home](/Hold%20The%20Flood/Coming%20Home) and [Home Projects](/Hold%20The%20Flood/Home%20Projects) are provisionally integrated after review204, response206 and final integration, disposition222. The cooperative loan/preparation scene allows listening, preparing canisters and reclaiming the same part; produced charge and communicated knowledge persist. Known panel location differs from uncertain pressure-line sampling, giving a concrete inspection without asserting remote safety or cause. Human reactions and contributions are explicit; emotional effect and the wider colony economy remain unvalidated. Lead owns the scene and Systems the contract; no second broad home review is pending. |
|||||||
|
26 | |||||||
|
27 | ## Completed written foundations |
||||||
|
28 | |||||||
|
29 | - [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. |
||||||
| 30 | - [Oxygen and Observation](/Hold%20The%20Flood/Oxygen%20and%20Observation): provisionally integrated record/display proposal. The owner decided that opening the journal pauses the rest of the game, including enemies and oxygen during combat; that requirement is in the brief. Other journal details and the wider oxygen rhythm remain proposed. |
|||||||
| 31 | - [Death and Persistence](/Hold%20The%20Flood/Death%20And%20Persistence): working proposal for persistent recoverable caches and retained records. Equipment availability and recovery journeys are costs. The suit baseline proposed in Build Rules answers the minimum-expedition dependency on paper; actual reach, part supply, abandonment and recovery viability remain unvalidated. |
|||||||
| 32 | - [Exploration Structure](/Hold%20The%20Flood/Exploration%20Structure): provisionally integrated fixed geometry with varying state, reach and access, concrete goal examples and narrative reinterpretation. Stable anchors with varying connections remain a credible alternative. Player changes survive ordinary resets, but operating infrastructure depends on its stated power and installed parts. |
|||||||
| 33 | - [Build Rules](/Hold%20The%20Flood/Build%20Rules): provisionally integrated connected equipment grammar, illustrative shared-part builds, causal-event rules and suit baseline. Navigation records traversed breadcrumbs without promising an unseen safe route; local equipment previews remain understandable while learned families help with unfamiliar objects and preparation. Fields, capacities and performance are not tuned or validated. |
|||||||
|
34 | |||||||
|
35 | 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. |
||||||
|
36 | |||||||
|
37 | [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. |
||||||
| 38 | ||||||||
|
39 | [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. |
||||||
| 40 | ||||||||
|
41 | [Discovery Chain](/Hold%20The%20Flood/Discovery%20Chain) and [Clues and Help](/Hold%20The%20Flood/Clues%20and%20Help) are provisionally integrated after review184, response186 and final PM corrections, disposition194. Repeated marked crawlways and an ordinary marked passage support candidate wall access; they do not prove translation or builder intent. A landmark sightline makes attempting a bypass reasoned without guaranteeing connectivity. Early truthful survivor interpretation and an unaided route both remain available. Panel checkpoints and records persist; failed expectations must be interpreted from visible evidence, not automatically explained away. One small fragment/use case does not fulfil a language requirement. Ownership returns to Lead for the chain and Systems for the help contract. No broad second review is pending. Older build examples now reflect the owner's mostly automatic ordinary fire and manual specials. |
||||||
| 42 | ||||||||
|
43 | ## Acceptance and remaining scope |
||||||
|
44 | |||||||
|
45 | 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. |
||||||
|
46 | |||||||
|
47 | The revival cause, station history, escape solution, language details, full rescue/colony systems, exact equipment economy, numerical oxygen rules and campaign content scope remain open. The 30/90/100–200 hour ambitions remain unproven. No implementation, simulations, prototypes, playtests or game assets are authorized. |
||||||
|
48 | |||||||
|
49 | PM coordinates ready handoffs during active sessions, with one-minute scheduled checks as a fallback while useful authorized work remains. Hourly checks apply only when no such work can continue. The [Team](/Hold%20The%20Flood/Team) page records the working agreement. Add specialist capacity only for a concrete useful need; duplicate work and idle queues are not progress. |
||||||