Blame
|
1 | # Hold The Horde — Design Coverage |
||||||
| 2 | ||||||||
| 3 | **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. |
|||||||
| 4 | ||||||||
|
5 | Across fifteen major areas, **twelve have usable first-pass contracts and three have examples or alternatives**. 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. |
||||||
|
6 | |||||||
|
7 | Three domains remain partial: regional progression, death/shifts/connections, and authored cast/short rescue. Accepted rules still need their finite inventories and integration before v1 is complete. Story And Ending Map30 supplies the newly usable story/ending contract; previously prepared categories are not counted again. This classification does not complete the five cast arcs/fifteen scenes,24module/40room, ten-encounter or twelve-mechanism inventories. |
||||||
|
8 | |||||||
| 9 | 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. |
|||||||
| 10 | ||||||||
| 11 | ## Remaining first-pass work |
|||||||
| 12 | ||||||||
| 13 | SMALL below is the outline's proposed planning sample, not an adopted game size. Counts help expose work and may change after the scope decision. |
|||||||
| 14 | ||||||||
| 15 | | Area | Coverage now | Concrete remaining v1 outcome | Dependency and work that can proceed | |
|||||||
| 16 | |---|---|---|---| |
|||||||
|
17 | | Expedition progression and regions | Partial: [Regional Discovery Map25](/Hold%20The%20Flood/Regional%20Discovery%20Map) prepared426 at3acda018, alongside the selected opening and outline | Twenty-four module and40placed-room v1 briefs linked to the prepared four-region/twelve-objective dependency map: proposed geometry/interfaces, actual contents, discovery/revisit purpose and access/recovery constraints; exhaustive instance variants remain M4 | Objective map closed18:32 Jerusalem. Final counts, ending destinations and physical joins remain replaceable until selected; the regional domain is still partial. | |
||||||
|
18 | | 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. | |
||||||
| 19 | | 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. | |
|||||||
|
20 | | Connected-build grammar | Usable [first-pass rules](/Hold%20The%20Flood/Build%20Rules) | Conversion, storage, saturation, readiness and rig/infrastructure conformance matrix | Narrow04 parent alignment integrated432 atb7b70875/42a0be59/2d6de3c0; PM retains STOPPED ownership of all three parents. Exact geometry/quantities may remain provisional; global rules, integration and pending owner choices remain open in04. | |
||||||
| 21 | | Equipment and acquisition | Usable twelve-part [catalogue](/Hold%20The%20Flood/Equipment%20Catalogue) and [acquisition/growth contract26](/Hold%20The%20Flood/Equipment%20Acquisition%20And%20Rig%20Growth), prepared434 atf5f6d768 | Source-fixture briefs and exception/recovery details, with concrete exemplar/port/material/source paths before any repair/adapter template becomes a usable route; provisional quantities and geometry | Closed18:57:01 Jerusalem after one focused critique/response and PM maintenance. All twelve paths, four starters/eight sources, three added fixtures and legal rig/property costs are prepared. The domain is not finished; acquisition preference and actual starter/capacity choices remain unselected. | |
|||||||
|
22 | | Combat and contested work | Usable [Combat Rules](/Hold%20The%20Flood/Combat%20Rules) and [combat-state contract27](/Hold%20The%20Flood/Combat%20And%20Enemy%20Roster), prepared443 | Remaining interface/edge-case matrix for controllers, target assistance, combined attacks, oxygen actions and recovery | Shared first-pass state sheet prepared19:34 atf1fe0d9a. Target assistance, multiple ordinary controllers and field healing remain proposals; exact timing and readability are unvalidated. | |
||||||
| 23 | | Enemies, encounters and traps | Usable [roster/pressure contract27](/Hold%20The%20Flood/Combat%20And%20Enemy%20Roster), prepared443, alongside five [trap families](/Hold%20The%20Flood/Traps%20And%20Encounter%20Progression) | Ten encounter-placement and twelve placed-mechanism v1 briefs: actual geometry/populations, cue variants, warning/work stages, reset/rearm/persistence and recovery; exhaustive variants remain M4 | Six ordinary/three special roles and two setpieces are prepared within ten encounters; ten of twelve mechanism slots allocated. Full inventories are still partial, and counts/origins remain replaceable proposals. | |
|||||||
|
24 | | Two alien languages and discovery | Usable [Two Language Discovery Map29](/Hold%20The%20Flood/Two%20Language%20Discovery%20Map), preparation-closed459 atdf0f48f5, alongside existing journal/utterance examples | Actual clue/string and physical-state variants, placed-room inputs/controls and both-order missed-evidence recovery briefs; final language origins and story remain unselected | Four proposed chains and two-language/two-register classification prepared20:23:52 after one focused critique/response. One local iris plate/input/state variant counted within the existing mechanism. Complete room placements, every clue permutation and comprehension validation remain unfinished. | |
||||||
|
25 | | Story, endings and corruption | Usable [Story And Ending Map30](/Hold%20The%20Flood/Story%20And%20Ending%20Map), preparation-closed466 at03c9cb8e, alongside existing alternatives | Actual clue/archival placements, isolation/diagnostic/culture state and scene variants, final canon/creative branches and owner-selected departure/save behavior | Four mystery/personal chains and apparent/deeper/optional-secret layers prepared20:42:22 after one focused critique/response; five proposed human scene variants still need unique cast/scene allocation. Captive/empty-core, treatment, reversibility and departure remain proposals. Credits/continue-before-departure versus permanently ending the save is now an unanswered fourth owner question; no phase or canon is selected. | |
||||||
| 26 | | Authored cast and short rescue | Partial: first-survivor alternatives and local examples; [Cast And Short Rescue Map31](/Hold%20The%20Flood/Cast%20And%20Short%20Rescue%20Map) submitted470, review under469 | Five SMALL cast briefs with motives, disagreements, bounded knowledge, contributions, short rescue outcomes and fifteen unique scene briefs, three primary scenes per person | Submitted20:53:50 atadb7b4a4; Systems STOPPED. One review under469 against criteriae87d7950 registered467. Draft21:30 target achieved early; reviewed22:30(22:00–23:30) remains forecast, today8Sep Jerusalem. First-survivor selection/global mortality affect specific branches; submission does not finish the cast inventory. | |
|||||||
|
27 | | Colony and home projects | Usable [Home And Colony Loop28](/Hold%20The%20Flood/Home%20And%20Colony%20Loop), preparation-closed450 at5bff3436, alongside Coming Home/Home Projects | Exact fixture/control and cue briefs, participant/facility state integration and owner-dependent management/economy branches; five final cast arcs/15scenes remain in the separate cast inventory | Closed20:01:12 Jerusalem after one focused critique/response. Living/death return, deliberate storage/sharing, refill, five optional projects and loan/reclaim are prepared, with two reused/three new projects and three new fixed ship fixtures. Counts/names/benefits remain proposed; first-survivor selection and gameplay validation remain open. | |
||||||
|
28 | | 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. | |
||||||
|
29 | | 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. | |
||||||
|
30 | | Content scope and production feasibility | Usable [first-pass scope contract](/Hold%20The%20Flood/Production%20Scope), prepared423 atc1a60388 | Deduplicated finite inventory, reuse assumptions, unique authoring/state costs, asset categories, Unity/Steam constraints and explicit scope cuts | PM24 closed423;144–247role-hourv1 planning allowance with explicit room/mechanism depth. Scope/band/cuts remain proposed; actual asset licences/specifications need checking. | |
||||||
|
31 | | 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. | |
||||||
|
32 | |||||||
| 33 | ## Work sequence and forecast |
|||||||
| 34 | ||||||||
| 35 | | Window, Jerusalem dates | Planned result | Staffing/dependency | |
|||||||
| 36 | |---|---|---| |
|||||||
|
37 | | 8 Sep | Story30 prepared466; prior contracts and narrow04 compatibility complete; Cast31 submitted470 | PM/GPT review work continues. Systems owns STOPPED Story30 and submitted Cast31; actual47020:53:50 follows verified receiving20:48:13.898. One review under469 against criteriae87d7950; no acceptance yet. Both original Claude roles stay paused; specialist setup9–10Sep remains planned, not active. | |
||||||
|
38 | | 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. | |
||||||
| 39 | | 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. | |
|||||||
| 40 | | 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. | |
|||||||
| 41 | | Target 10 Nov; likely 20 Oct–1 Dec | Detailed finite authored campaign specification | Low-confidence estimate until an inventory and representative detailed packages are checked. | |
|||||||
| 42 | ||||||||
| 43 | The core target remains **11 September (10–14 September)**. These are planning estimates, not guarantees or demonstrated playtime. The next substantive re-estimate is **9 September at 18:00 Jerusalem**. Early completion of a local written package does not by itself justify bringing the whole-wiki date forward. |
|||||||
| 44 | ||||||||
|
45 | Shared integration outcome04’s narrow parent-equipment alignment432, legacy Discovery Chain/Expedition slice441–443 and Coming Home/Home Projects compatibility456 are complete. The legacy slice replaces stale route/journal clauses with no new access guarantee;456 aligns home parts/supply, deliberate unloading, historical routes and refill conservation, with PM STOPPED ownership of both home parents. Remaining global shift/rescue/full-station branches and other affected articles still need integration;04 stays open. A pending choice blocks only the rules that actually depend on it, not every parallel stream. |
||||||
|
46 | |||||||
| 47 | ## Estimate accounting |
|||||||
| 48 | ||||||||
| 49 | 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. |
|||||||
| 50 | ||||||||
|
51 | 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 the dated8Sep planning estimate, not logged labor or an automatically current remaining balance; subtract accepted scope before recomputing the remainder. |
||||||
|
52 | |||||||
|
53 | This map is based on the current owner brief, Whole Game Outline revised through narrow alignment432 at2d6de3c0, 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 closed423 after scoped response421/422; Regional Discovery Map25 closed426 after response425 at3acda018. Its objective map leaves the domain partial pending24module/40room briefs. Acquisition26 closed434 at18:57:01, finalf5f6d768, after actual429, one focused critique431, the verified author response and PM’s paragraph-only maintenance433. Late notice436 records pre-maintenancef7ede725 rather than a rollback. PM now classifies equipment/acquisition as a usable first-pass contract, with source-fixture detail and exceptions still required. Combat And Enemy Roster27 closed443 at19:34, finalf1fe0d9a, after one focused critique and the442 response. PM now classifies the existing enemy/encounter/trap category as usable first-pass; the already usable combat category is not counted again. Exact40room/ten-encounter/twelve-mechanism inventories remain incomplete. Home And Colony Loop28 closed450 at20:01:12, final5bff3436, after one focused critique and449response. Home/colony was thereby classified usable first-pass; five final cast arcs/15scenes and exact fixture/control details remain unfinished. Two Language Discovery Map29 closed459 at20:23:52, finaldf0f48f5, after one focused critique and458response. Language/discovery was thereby classified usable first-pass. Story And Ending Map30 closed466 at20:42:22, final03c9cb8e, after one focused critique and465response. Only the existing story/ending category now advances, bringing the current total to12usable/3partial. Cast And Short Rescue Map31 was submitted470 at20:53:50, sourceadb7b4a4, with independent criteriae87d7950 registered467; one review proceeds under469 and Systems STOPPED. Cast remains partial until the scoped submission is dispositioned. The newly asked credits/continue-before-departure versus permanent save-ending choice remains unanswered, alongside the three earlier owner questions. Narrow legacy04 Discovery114e9267/Expedition836ab2ae integration is verified443; global04 remains open. Scope estimates are reviewed planning assumptions, not validated labor or adopted content counts. 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. |
||||||
