2026-09-08 18:21:01
Anonymous:
Clarify v1 room and mechanism brief obligations and uniquely account for their remaining work
hold the flood/design coverage.md ..
@@ 2,7 2,7 @@
**PM coverage assessment, 8 September 2026.** This is the remaining-work map for the [whole-game outline](/Hold%20The%20Flood/Whole%20Game%20Outline), alongside the dated [Progress and forecast](/Hold%20The%20Flood/Progress). It is management work, not an additional completed gameplay package.
-
Across fifteen major areas, **five have usable first-pass contracts, eight have examples or alternatives, and two still need a dedicated contract**. These are coverage categories, not weighted progress or a percentage of the game. Even an area with usable rules still needs its finite content, edge cases and integration. “Written” does not mean owner-approved, implemented or validated.
+
Across fifteen major areas, **six have usable first-pass contracts, eight have examples or alternatives, and one still needs a dedicated prepared contract: production**. These are coverage categories, not weighted progress or a percentage of the game. Even an area with usable rules still needs its finite content, edge cases and integration. “Written” does not mean owner-approved, implemented or validated.
The first complete wiki must describe actual behavior, progression and consequences across every major area. It may use clearly labelled provisional defaults and numerical tuning; a major area left only as “TBD” does not qualify. The later detailed-content milestone specifies the individual authored rooms, clues, encounters and scenes.
@@ 12,27 12,27 @@
| Area | Coverage now | Concrete remaining v1 outcome | Dependency and work that can proceed |
|---|---|---|---|
-
| Expedition progression and regions | Examples: [opening](/Hold%20The%20Flood/First%20Expedition%20Options), outline | Four-region, twelve-objective SMALL dependency map: discoveries, return value, alternate access and build/cast/language gates | Draft now. Final counts, ending destinations and physical joins remain replaceable until selected. |
+
| Expedition progression and regions | Partial: [opening](/Hold%20The%20Flood/First%20Expedition%20Options), outline; [Regional Discovery Map25](/Hold%20The%20Flood/Regional%20Discovery%20Map) submitted under418, in focused review | Four-region/twelve-objective dependency map plus24module and40placed-room v1 briefs: proposed geometry/interfaces, actual contents, discovery/revisit purpose and access/recovery constraints; exhaustive instance variants remain M4 | Systems owns25; reviewed19:30(19:00–20:00) today Jerusalem. Final counts, ending destinations and physical joins remain replaceable until selected. |
| Death, shifts and station connections | Conditional [joining mechanism](/Hold%20The%20Flood/Connecting%20The%20Station) | One shared rule set for death order, room/object identity, permanent joins, recovery, rescue interaction and whole-station completion | Local permanence is already selected. The final-layout answer affects the rigid candidate; identity and recovery requirements can proceed now. |
| Oxygen, condition and carrying | Usable [first-pass rules](/Hold%20The%20Flood/Survival%20And%20Loadout) | Variant/edge-case matrix and provisional opening quantity sheet | No owner answer blocks paper variants. Pressure and balance need later authorized evidence. |
| Connected-build grammar | Usable [first-pass rules](/Hold%20The%20Flood/Build%20Rules) | Conversion, storage, saturation, readiness and rig/infrastructure conformance matrix | Draft now; exact geometry and quantities may stay provisional. New catalogue behavior must be reconciled with the shared rules. |
| Equipment and acquisition | Twelve-part [catalogue](/Hold%20The%20Flood/Equipment%20Catalogue) preparation-closed400; [acquisition alternatives](/Hold%20The%20Flood/Progression%20Options) | Catalogue plus source/acquisition map, material uses and exception rules | Catalogue behavior is prepared. Found parts versus fabrication is unselected, but neither blocks observable part design. |
| Combat and contested work | Usable [first-pass rules](/Hold%20The%20Flood/Combat%20Rules) | Shared combat state sheet linking auto-fire/manual specials, controllers, oxygen actions, interruption and recovery | Draft now; targeting assistance and field healing remain proposals. Readability is unvalidated. |
-
| Enemies, encounters and traps | Three [creatures](/Hold%20The%20Flood/Horde%20Creature%20Proposals), five [trap families and regional map](/Hold%20The%20Flood/Traps%20And%20Encounter%20Progression) prepared410 | Complete roster/pressure specification and twelve placed SMALL mechanism instances, with actual geometry, reset/rearm boundaries and discovery links | First-pass families/map are prepared; exact placements, combined encounters and roster coverage still need authoring. Origins remain replaceable hypotheses. |
+
| Enemies, encounters and traps | Three [creatures](/Hold%20The%20Flood/Horde%20Creature%20Proposals), five [trap families and regional map](/Hold%20The%20Flood/Traps%20And%20Encounter%20Progression) prepared410 | Complete roster/pressure specification plus twelve placed SMALL mechanism v1 briefs with first-version geometry, warning/work stages, reset/rearm/persistence, recovery and discovery links; exhaustive variants remain M4 | First-pass families/map are prepared; exact placements, combined encounters and roster coverage still need authoring. Origins remain replaceable hypotheses. |
| Two alien languages and discovery | [Expedition example](/Hold%20The%20Flood/Language%20Expedition), journal rules, [testable interaction](/Hold%20The%20Flood/Alien%20Utterance%20Discovery) | Four SMALL discovery chains across both languages: evidence, competing interpretations, discriminating action, correction and later use | Draft operational chains now. Define how visitor marks and utterance registers relate; a response alone does not prove request semantics or a god. |
| Story, endings and corruption | [Story](/Hold%20The%20Flood/Hospital%20Story%20Directions) and [corruption alternatives](/Hold%20The%20Flood/Resurrection%20And%20Corruption) | Beat/evidence/consequence map through apparent, deeper and optional secret layers, including visible ending choices and colony consequences | Final canon needs owner choices. Draft the causal alternatives now; no automatic death budget, ending lock or mandatory treatment. |
| Authored cast and short rescue | Two [first-survivor alternatives](/Hold%20The%20Flood/First%20Survivor) and local examples | Five SMALL cast briefs: motives, disagreements, bounded knowledge, home contribution, three-scene arc and short rescue outcomes | The first-survivor choice and global mortality affect specific branches. Other characters and living crossings can proceed. |
| Colony and home projects | [Home example](/Hold%20The%20Flood/Coming%20Home), [cooperative project](/Hold%20The%20Flood/Home%20Projects) | Home-loop state map and five person-linked projects with voluntary contributions, results and equipment reclaim | Draft using an explicit provisional no-upkeep baseline. A management economy needs an owner decision before adoption. |
| Information, controls and accessibility | Usable [first-pass contract](/Hold%20The%20Flood/Player%20Information) | Cue/interaction inventory, journal/manifest structure and option/default interactions, including non-colour/non-audio equivalents | Most work can proceed. Mechanical uncertainties affect their particular displays. Full journal pause is settled. Existing article ownership must be respected. |
-
| Save, identity and content authoring | Dedicated contract submitted413; focused review active | Design-only save/resume, death transaction, room/item/record identity, authored-content versions and recovery requirements | Systems23 submitted; review/response before preparation closeout. Final shift/rescue order affects transaction ordering; proposed defaults must not invent an owner save policy. Engineering/migrations remain later. |
-
| Content scope and production feasibility | Dedicated game-specific contract missing | Deduplicated finite inventory, reuse assumptions, unique authoring/state costs, asset categories, Unity/Steam constraints and explicit scope cuts | Cost alternatives now. Scope commitments and purchases need owner approval; verify current licences/specifications when considering actual assets. |
+
| Save, identity and content authoring | Usable [first-pass contract](/Hold%20The%20Flood/Save%20And%20Content%20State), preparation-closed417 at438cdf35 | Complete transition/commit catalogue, placement/reference matrix and resolved conditional branches and recovery policy | First-pass identity/continuity requirements are prepared. Save policy, rescue/shift order and full-station behavior remain open; engineering/migrations remain later. |
+
| Content scope and production feasibility | Dedicated prepared contract still missing; [Production Scope24](/Hold%20The%20Flood/Production%20Scope) submitted under418, in focused review | Deduplicated finite inventory, reuse assumptions, unique authoring/state costs, asset categories, Unity/Steam constraints and explicit scope cuts | PM owns24; reviewed19:40(19:05–20:10) today Jerusalem. Draft hours remain unreviewed; scope commitments/purchases need owner approval, and actual asset licences/specifications require checking. |
| Development and validation handoff | Usable [first-pass plan](/Hold%20The%20Flood/Development%20And%20Validation%20Handoff), prepared410 | Final v1-specific packet with exact revisions, development scope, conditions, staffing, estimates and decision criteria | Eleven risks/gates are mapped, including sustained progression. Actual prototypes, code, simulations, assets and playtests require explicit phase authorization. |
## Work sequence and forecast
| Window, Jerusalem dates | Planned result | Staffing/dependency |
|---|---|---|
-
| 8 Sep | Catalogue, trap/encounter and handoff first passes prepared; coverage map published; save/content-state contract underway | PM and existing GPT Systems continue. Both Claude roles stay paused until the owner confirms their return. |
+
| 8 Sep | Catalogue, trap/encounter, handoff and save/content-state first passes prepared; Production24 and Regional Map25 submitted under418, in focused review | PM and existing GPT Systems continue. Both Claude roles stay paused until the owner confirms their return. |
| 9–11 Sep, core buffer to 14 Sep | Shared core rules and identity requirements; start region, cast, language and production work | Two additional specialist setups planned 9–10 Sep. Ready scopes, not provider availability alone, determine assignments. |
| 14–18 Sep | Domain designs and finite inventories sufficiently concrete for cross-domain review | Content counts and major story/mechanism choices must be dispositioned or visibly provisional. |
| Target 22 Sep; likely 18–29 Sep | Complete first-pass wiki with integrated interfaces and a development handoff outline | PM integration and review are on the critical path; more writers do not remove that work. |
@@ 46,6 46,6 @@
The outline's **111–208 role-hours is a partial original specification allowance, not remaining labor**. Its survival and information first-pass packages are now prepared. The later survival22–39 and information35–59 role-hour envelopes describe deeper inventories; they are not measurements of elapsed effort and must not simply be added to the old total. Equipment's first-pass allowance likewise differs from its later detailed catalogue.
-
Track deliverable and depth separately: first-pass rule set, finite content inventory, and later implementation. Count a shared survivor scene/colony project/clue/region objective once, then estimate only its distinct additional work. Keep package review/response, PM cross-page integration and whole-game coherence review separate without double counting. Reconcile these scopes before publishing a new remaining-hours total.
+
Track deliverable and depth separately: first-pass rule set, finite content inventory, and later implementation. Count a shared survivor scene/colony project/clue/region objective once, then estimate only its distinct additional work. Keep package review/response, PM cross-page integration and whole-game coherence review separate without double counting. Production24's response explicitly assigns the24module/40room/12mechanism v1 brief minimums to one20–34author-hour package, beyond objective allocation. This retains the placed-mechanism obligation rather than silently deferring it. Detailed campaign authoring extends these briefs; do not charge both full depths. See [Production Scope](/Hold%20The%20Flood/Production%20Scope) for the proposed revised144–247role-hour v1 allowance and separate review/response/integration; it is a planning estimate, not logged labor.
-
This map is based on the current owner brief, Whole Game Outline revision65595abf, the linked owning articles and a source-by-source PM coverage audit. The catalogue was subsequently read at submission396, received one focused review/response397/399 and was preparation-closed400 at revision737b3cfd. Outcome21 trap/encounter and22 handoff first passes were closed410;23 save/content-state is assigned411. The separately found Rescue Shift Proposal and Station Assembly Example remain unadopted intake407, not completed shared integration. The management checkpoint retains the exact inspected source revisions. No page count, model agreement or desk review establishes fun, balance, usability, performance or campaign duration.
+
This map is based on the current owner brief, Whole Game Outline revision65595abf, the linked owning articles and a source-by-source PM coverage audit. The catalogue was subsequently read at submission396, received one focused review/response397/399 and was preparation-closed400 at revision737b3cfd. Outcome21 trap/encounter and22 handoff first passes were closed410;23 save/content-state closed417 at18:09:56 Jerusalem, final438cdf35. Production24 and Regional Discovery Map25 were assigned418; their drafts and estimates are not reviewed outcomes. The separately found Rescue Shift Proposal and Station Assembly Example remain unadopted intake407, not completed shared integration. The management checkpoint retains the exact inspected source revisions. No page count, model agreement or desk review establishes fun, balance, usability, performance or campaign duration.
