2026-09-08 14:07:21
Anonymous:
Adopt owner shift and short-rescue directions; develop revisable hospital draft in parallel
hold the flood/design plan.md ..
@@ 1,51 1,46 @@
# Hold The Horde — Design Plan
-
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.
+
Design a discovery-first survivorlike under the [Owner Brief](/Hold%20The%20Flood/Brief), with expressive builds, meaningful hordes and an authored colony. Written comparisons establish proposals and dependencies; they do not demonstrate fun, balance, accessibility, production feasibility or campaign duration. This phase remains design only.
-
## Current work: concrete proposals for owner reaction
+
## Current owner direction
-
The owner accepted connected equipment combinations, shared oxygen/equipment/loot capacity, practical clue-based exploration and the route/work horde rhythm. All carried property returns home on death; equipment loans at home are tentative. The persistent-station and cooperative-rescue examples have been explained, but the owner has not yet reacted to those explanations. The [Owner Brief](/Hold%20The%20Flood/Brief) records the exact scope.
+
The station shifts after each death, preserving uncertainty about what is where. Selected player changes, such as unlocked doors, remain permanent. This supersedes the fixed-layout proposal. Cooperative rescue is accepted provided it does not become a long escort quest. Everything still carried returns aboard on death; completed work persists, the journal pauses the whole game, and ordinary combat uses mostly automatic fire with manual specials. Linked reusable parts, shared oxygen/equipment/loot capacity, practical clue exploration and route/work hordes are accepted directions. Home equipment loans are tentative.
-
The owner-decision integration is complete after actual-source review and final disposition269. The old compressor-object fragility gate was removed as a provisional simplification of that example, without deciding all equipment condition rules. No death cache, compulsory live delivery or substitute confiscation remains in the integrated rules.
+
The leading story is now the owner's **early, fully revisable hospital draft**: ancient aliens attempted godhood and abandoned the station; humans made it a hospital because of extraordinary healing and revival; research revealed a captive god in the core, and medical systems became harmful. Repeated revival and the experiments of both eras could explain the creatures. Every narrative detail remains open. This does not automatically adopt a player death counter, transformation deadline, specific ending or retrieval mechanism. The former Registry/Unit/Clinic comparison is no longer an unanswered equal-choice gate.
-
Systems266 is composing **Progression Options**: two concrete equipment-growth experiences, each showing acquisition, an exact useful build, a discovery that changes its use, missed finds and the reason to go out again. Both saved independent originals were read, byte-hash verified and jointly released264/265. Systems supplies practical comparison rather than a third preference vote; the two originals' A/B labels describe different design axes. Owner-readable choices come before extensive cross-page refinement.
+
## Active outcomes
-
Lead and Reviewer268 each have two independent **station-district expedition pitches** to prepare: a distinctive place, a visible discovery that changes an action, a meaningful horde situation and a reason to return. Their new ideas remain private until both originals are saved and jointly released. These selectable content proposals do not require a central-story choice or fixed-map approval. Delivery is currently unavailable: both pinned Claude sessions were absent from fresh native registries, so neither message was sent. PM is handling host recovery; Systems work continues. There is no replacement role or permission change.
+
| Role | Bounded outcome | Current dependency |
+
|---|---|---|
+
| Systems | Three Horde Creature Proposals completed and read by PM; final narrow coherence correction preserves their counterplay | Ready as selectable proposals, not an adopted roster |
+
| Systems | Two independent shifting-station models, each with a concrete before/after-death journey, persistent work, useful historical records and a short-rescue example | Working on276; PM has separately saved an independent position, with both originals withheld until joint release |
+
| Design Lead and Independent Reviewer | Each independently develops two causal versions of the owner's hospital/godhood draft, including concrete discoveries and consequential player actions |Working on277 after verified automatic delivery to both original Claude sessions; undelivered268 is superseded |
+
| PM | Relay owner answers, verify actual outputs, release independent positions together and present concise proposals early | Original Claude connections recovered under their existing identities; no owner handoff text required |
-
## Completed language comparison
+
The PM marked conflicting old rules in their owning articles after a source impact audit. Permanent map placement is superseded; remembered positions are historical; death/rescue ordering is unresolved. The next consolidated update will follow a concrete shift comparison. Do not silently treat the former fixed-anchor alternative as owner-selected, or invent destruction, duplication or survivor loss to handle a shift.
-
[Language Expedition](/Hold%20The%20Flood/Language%20Expedition), [Language and Journal](/Hold%20The%20Flood/Language%20and%20Journal) and [Language Design Evidence](/Hold%20The%20Flood/Language%20Design%20Evidence) are provisionally integrated after focused review252, response254 and final source disposition269. Two observed mains support a tentative word-order reading; visible transfers support local source/receiver roles. A material connection plus service access gives a lead to investigate, without proving a continuous walking route or shorter journey.
+
## Ready for reaction
-
The journal records actual arrivals or incomplete attempts without grading freeform meanings. Fallible on-request visual suggestions and manual comparison remain available; survivor help is truthful and attributed. These assistance choices are reversible proposals. The full pause, including enemies and oxygen during combat, is required by the owner. Sources support uncertainty and repeated-context precedents but do not establish this game's enjoyment, comprehension, accessibility or content feasibility. No second broad review, full conlang, artwork, implementation or playtest is assigned. Lead owns the expedition, Systems the journal contract, Reviewer the evidence; all three sources are stopped until a relevant new assignment.
+
[Horde Creature Proposals](/Hold%20The%20Flood/Horde%20Creature%20Proposals) offers a telegraphed pressure-wave creature, a moving screen for a crowd and a readable oxygen-tether attacker. All can be avoided, interrupted or defeated, and a strong rig may overwhelm them. Their origins are replaceable candidates from either experimental era.
-
## Story directions awaiting owner reaction
+
[Progression Options](/Hold%20The%20Flood/Progression%20Options) compares claiming functioning components from station machinery with observing their behaviour and fabricating chosen parts aboard. Both include useful legal build traces, changed uses of old parts and motivation for another expedition. The two independent originals were read, hash-verified and jointly released before Systems' practical comparison; preparation closed272. No economy, starting loadout, fabrication bench or installed-object persistence model has been selected. Comparative claims about surprise, targeting and attachment remain expectations rather than measurements.
-
The three concrete pitches from [Mystery Directions](/Hold%20The%20Flood/Mystery%20Directions) and [Mystery Consequences](/Hold%20The%20Flood/Mystery%20Consequences) have been presented to the owner. They propose an active alien Registry, a secretly fitted recovery Unit with an outside sponsor, or an automated experimental Clinic. The strongest versions distinguish departure clearance from service cancellation, make causal eligibility explicit and offer a concrete deeper intervention. Each now preserves owner-required carried-property return.
+
The previous [Mystery Directions](/Hold%20The%20Flood/Mystery%20Directions) and [Mystery Consequences](/Hold%20The%20Flood/Mystery%20Consequences) preserve alternatives and costs for reference. Their protected triage, registration and sponsor mechanisms do not constrain development of the owner's new draft. New independent story positions will be shown before extensive cross-article refinement.
-
These are candidate stories with costs, not adopted central answers. No owner reaction has arrived yet. Ordinary revival continues through deeper play in each proposed baseline; final departure ends it. Global survivor mortality or a named eligibility exception remains separate. Comparison preparation closed247 and owner-return integration269; no further broad story review is pending. Ownership remains Lead for Directions and Systems for Consequences.
+
## Existing written foundations
-
[Coming Home](/Hold%20The%20Flood/Coming%20Home) and [Home Projects](/Hold%20The%20Flood/Home%20Projects) remain provisionally integrated under222, with loans now tentatively accepted by the owner. The scene permits listening, canister preparation and reclaiming the same loaned part. Charge and communicated knowledge persist; known panel location is distinct from uncertain pressure-line sampling. Human contributions are explicit; emotional effect and the full colony economy are still unvalidated. Lead owns the scene and Systems the rules.
-
-
## Completed written foundations
-
-
- [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.
-
- [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.
-
- [Death and Persistence](/Hold%20The%20Flood/Death%20And%20Persistence): the owner requires carried equipment and new loot to return aboard on death. Resources already consumed remain spent and deliberately left objects do not duplicate. Records and completed work persist. The basic suit is a separate proposal, with no compulsory cache-recovery role. Further persistence details and survivor outcomes remain scoped proposals or undecided questions.
-
- [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.
-
- [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.
-
-
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.
-
-
[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.
-
-
[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.
+
- [Expedition Proposal](/Hold%20The%20Flood/Expedition%20Proposal), [Build Comparison](/Hold%20The%20Flood/Build%20Comparison) and [Build Rules](/Hold%20The%20Flood/Build%20Rules): linked reusable parts, contrasting rigs, causal-wave rules and shared carrying choices. Exact grammar, capacity, part catalogue and starting equipment remain proposals. The compressor example no longer requires live delivery or an uncracked object.
+
- [Exploration Structure](/Hold%20The%20Flood/Exploration%20Structure) and [Death and Persistence](/Hold%20The%20Flood/Death%20And%20Persistence): safe carried-property return and retained work remain; the old fixed geometry requires replacement with the new shift direction.
+
- [Oxygen and Observation](/Hold%20The%20Flood/Oxygen%20and%20Observation), [Discovery Chain](/Hold%20The%20Flood/Discovery%20Chain) and [Clues and Help](/Hold%20The%20Flood/Clues%20and%20Help): readable survival state, captured evidence, voluntary investigation and truthful bounded survivor help. Prior geographic observations cannot guarantee current routes after a shift.
+
- [Horde Encounters](/Hold%20The%20Flood/Horde%20Encounters) and [Combat Rules](/Hold%20The%20Flood/Combat%20Rules): route crowds and selected contested work, with persistent completed stages and strong builds allowed to succeed. Targeting and individual creature behaviour remain proposals.
+
- [Rescue and Home](/Hold%20The%20Flood/Rescue%20and%20Home) and [Rescue Rules](/Hold%20The%20Flood/Rescue%20Rules): a short cooperative crossing remains useful. Finite multi-stage routes need to meet the owner's short-rescue condition, and death/shift/abort ordering still needs a coherent contract.
+
- [Coming Home](/Hold%20The%20Flood/Coming%20Home) and [Home Projects](/Hold%20The%20Flood/Home%20Projects): a tentative loan, canister preparation and human contributions. Prepared charge and communicated knowledge persist; the whole colony economy and emotional effect remain unvalidated.
+
- [Language Expedition](/Hold%20The%20Flood/Language%20Expedition), [Language and Journal](/Hold%20The%20Flood/Language%20and%20Journal) and [Language Design Evidence](/Hold%20The%20Flood/Language%20Design%20Evidence): observable repeated contexts, partial interpretations, factual arrival/incomplete records and fallible requested visual assistance. These completed focused review252 and response254, with final integration269. A transfer connection never proves a walking route. Historical evidence needs to be reconciled with shifting layouts; this does not require another whole-language review or a full conlang.
## 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.
+
Preserve clear immediate goals and understandable controls while discoveries change the meaning or use of familiar things. Judge concrete player choices and costs, not agreement counts, provider confidence or prose volume. Independent first positions precede new peer recommendations; a focused critique and response lead to PM disposition, not a unanimity loop. Articles retain one writer, and current-live-versus-proposed diffs and readback protect shared work.
-
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.
+
The hospital draft's causes and ending, player consequences of resurrection corruption, shift/persistence rules, short rescue logistics, full colony systems, language details, equipment economy, numerical oxygen rules and campaign scope remain open. The 30/90/100–200hour ambitions are unproven. No game implementation, prototypes, simulations, playtests or assets are authorised. No AI art. Purchases and rare custom/authored assets require owner approval.
-
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.
+
PM follows ready handoffs during active work, with one-minute scheduled checks as a fallback while useful authorised work exists. Local hosts must remain available. Routine unchanged checks stay quiet; substantive proposals, decisions and actionable outages are reported. Add specialist capacity only for a demonstrated need.
