Across fifteen major areas, **seven have usable first-pass contracts and eight 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.

| 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. |

| 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. |

| 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. |

| 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. |

| 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. |

| 8 Sep | Catalogue, trap/encounter, handoff and save/content-state first passes prepared; Production24 prepared423; Regional Map25 draft420 in focused review | PM and existing GPT Systems continue. Both Claude roles stay paused until the owner confirms their return. |

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 closed417 at18:09:56 Jerusalem, final438cdf35. Production24 closed423 after scoped response421/422; Regional Discovery Map25 draft420 remains in review. 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.