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

Seven domains remain partial, and accepted rules still need their finite inventories and integration before v1 is complete.

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

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

| 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, save/content-state, Production24, Regional Map25 and Acquisition26 first passes prepared;04 narrow parent alignment432 complete; Combat27 authoring toward draft19:45 and reviewed20:30 | PM and existing GPT Systems work continues; actual27 receiving18:58:15.181 Jerusalem verified. Both Claude roles stay paused until the owner confirms their return. |

Shared integration outcome04’s narrow parent-equipment alignment is complete432. Its remaining owner-dependent branches must replace obsolete fixed-map and long/multiple-refuge assumptions in article bodies, rather than accumulating warning banners. A pending choice blocks only the rules that actually depend on it. It does not suspend the rest of the design.

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 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 is active under435 with one native handoff and actual receiving15:58:15.181UTC verified; its roster does not complete the twelve placed-mechanism briefs. 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.