**2026-09-07 · [Full findings and exact source revisions](/Hold%20the%20Flood/PM%20Reviews/PMR008).** PMU008's Visionary-first priority above remains primary. This review updates the evidence behind the older PMR007 rows; those rows are historical, not instructions to redo completed work.

| Owner / work | Current disposition | Next bounded action |

| --- | --- | --- |

| Visionary + Lead / player experience | Initial Brief vision received; [Campaign de4893](/Hold%20The%20Flood/Campaign?revision=de4893) is an integrated contribution, not an accepted experience | Existing PMU008 vision/expedition deliverable remains due. Address the 3:30–8:00 wait and explain Siphon's extra margin when Heavy fuel alone already covers the crossing; preserve meaningful alternatives and earned shortcuts. Do not expand content to meet an old review checklist |

| Lead / DES105 | Heavy continuity, named shelter, exposure accounting and notation credited | Correct activation/expiry versus 9:40 extraction, committed versus consumed planted charge, retargeting at expiry, “before” the 8:00 dispatch, “tram not an option,” and five versus four empty cells. Correct X35's stale criterion-11 count. Exact findings: PMR008 §1/3 |

| Independent Critic / REV105 | [42ad46](/Hold%20The%20Flood/Design%20Review?revision=42ad46) accepted as a review contribution with PM qualifications | Recheck successor timeline; do not accept 80 seconds ending within 40. Creative closure requires a worthwhile decision, not merely an unavoidable second surge. On next edit, scope Findings-index footer to archived rounds |

| World / WLD104; Colony / COL102; Equipment / EQP102 | Targeted corrections accepted: [744b21](/Hold%20The%20Flood/World%20And%20Mystery?revision=744b21), [59ad65](/Hold%20The%20Flood/Colony?revision=59ad65), recording reconciliation [6d6d1d](/Hold%20The%20Flood/Equipment/Build%20Paths?revision=6d6d1d) | No repeat of delivered chronology, grounded persistence, D026 or shelter fixes. Reconcile only interfaces changed by the vision/scene revision; Q52 current plain-language openings remain due |

| Combat / CMB102; Enemies | Old live-copy conflicts and approach countersign accepted at [221c48](/Hold%20The%20Flood/Mechanics/Combat?revision=221c48); duplicate accounting removed at [56cadb](/Hold%20The%20Flood/Enemies?revision=56cadb) | Qualify §7's readability prediction and “combination costs nothing”; no new roster or composition quota |

| District designer + Lead / CAM102–103 | Collector notches accepted [8e39d2](/Hold%20The%20Flood/Districts/The%20Collector?revision=8e39d2); redundant-trip audit accepted [c1bbe1](/Hold%20The%20Flood/Districts?revision=c1bbe1). Exchange [4d6703](/Hold%20The%20Flood/Districts/The%20Exchange?revision=4d6703) still has bounded issues | Retain Exchange's six-cell issue, field bundle, shelter relink and legal distances as corrections to any retained scene. Lead scopes dispatch cadence and terminal positions. The current 34-trip estimate is unmeasured and partly extrapolated; no padding |

| Reader + Editor / Q52–54 | Equipment reorder reversal accepted at [ba5942](/Hold%20The%20Flood/Equipment?revision=ba5942); Q52 still open. Q54 Hub guidance being corrected in this review | Verify saved Hub for Q54. Keep Q52 truthful-current summaries and Q53 index pointers under PMU008; correct stale “nothing open” header and distinguish build families from items. Do not redo the reversal |

| Reference Researcher / REF112 | [ca6543](/Reference/Readability%20Formulas?revision=ca6543) has a provenance/comparison defect | Owner rejected PM's PPTX, not the measured Campaign excerpt. Remove claimed demonstrated misranking: 1.8-point gap is within stated uncertainty and 4.7× density uses another text pair. Keep appropriately attributed general limitations; no new metric study |

Existing asset-gap audit remains unresolved; no purchase, custom art, new agent or development approval is requested. The next owner-facing milestone remains the concrete vision and expedition, not another status deck.

**Owner instruction:** after PM's state-of-design report, the owner said “sounds good. resume.” The overnight pause is lifted for the design process. PM's hourly review is enabled. This is approval to continue design work under the recommended priorities, not approval of the game design, a district/hour target, purchases, authored assets or development. Existing specialists retain ownership; a wiki assignment does not establish that another chat has resumed.

**Next deliverable:** demonstrate why later expeditions remain worth taking. Integrate rule corrections with build experimentation, discoveries that change a plan, and meaningful refuge choices. More pages, item names, enemy counts or arithmetic consistency alone will not satisfy this pass. The existing seven-district baseline is provisional; no new count quota is imposed.

| Task | Owner | State | Bounded deliverable and acceptance evidence |

| --- | --- | --- | --- |

| DES105 | Existing Lead | Ready; integrates ongoing DES104 corrections | One concise revision of Campaign showing a first visit, a changed return and a later return to the same district, connected to the wider campaign. State what the player previously believed, newly learns, prepares differently, tries, sacrifices and changes. Include a credible alternative on each return and the lasting consequence. Link domain detail; no new omnibus document. |

| EQP102 / CMB102 | Existing Equipment and Combat designers | Ready; joint contribution to DES105 | In Build Paths and Combat, show three materially different strategies for the same expedition objective, then how one discovery enables a combination that changes a later approach. Trace acquisition, legal rack, fuel, targeting and enemy counterplay; show where each strategy fails or sacrifices an opportunity. Explain whether the present catalogue supports this or which specific addition/revision earns its cost. Three named families and unexplained combinatorial counts are insufficient. |

| WLD104 | Existing World and Mystery designer | Ready; contribution to DES105 | Supply one campaign-spanning clue chain with at least two changes in the player's explanation, each producing a different route, equipment choice or machine operation before the ending. Include observable evidence, a plausible wrong interpretation, a safe way to investigate it, redundant essential access and a payoff. State what remains worth discovering after the central answer is understood. |

| COL102 | Existing Colony designer | Ready; contribution to DES105 | Show two competing refuge-development approaches across those same returns: what each investment changes on the next trip, what opportunity it gives up and how failure affects recovery. Assess whether one active support assembly offers enough colony choice; argue to retain or revise it using player decisions. Preserve the no-mandatory-upkeep/free-return baseline unless explicitly proposing a reasoned change. |

| CAM103 | Existing Campaign designer | Ready; contribution to DES105 | Place the repeat-visit sequence in actual district geography and distinguish new discovery, changed-world revisit and repeated traversal. Identify any baseline trip whose only purpose is hauling or repeating a solved interaction; cut, combine or redesign it. Keep scope/duration conditional on the resulting content. Coordinate transfer of Lead-authored districts with attribution. |

| REV105 | Existing Independent Design Critic | Ready when the combined DES105 revision exists | Judge the exact integrated sequence against exploration, experimentation, mystery and survivorlike combat. Can the later visit be played by repeating the first solution? Are alternate builds real choices under the written rules? Does evidence change action before the finale? Does colony investment matter? Report the strongest failure and smallest useful repair; do not claim empirical enjoyment or balance. |

**Existing correction work remains active, with current-source checks.** PMR006 remains the last completed PM checkpoint. The interrupted pre-pause intake did not publish a new acceptance verdict. Submissions after PMR006 must be reviewed at their actual revisions before closure; do not redo a correction already delivered merely because an older row below still requests it. In particular, Tasks now reports Combat r6 / Enemies r8 and mirrored Spark/Floater rulings; that is submission evidence, not PM acceptance.

The pre-pause Exchange 5bc625 illustration relied on early and overlong lure power; Collector 75c09e specified a five-second winch against two-second Coil power. CAM102 and the Lead must check current successors and correct these if still present: show earned charge and actual lure expiry/retargeting, and an explicit powered/manual mechanism with retained progress or another legal choice. Do not lengthen the shared pulse simply to rescue a scene.

**Asset follow-through:** Reference/Asset Audit is REF110 (REF109 is Electroreception). Source/licence discovery is useful evidence; it does not establish style fit, animation/pose coverage or suitability. Lead and Reference should separate located candidates, reuse/adaptation work and unresolved presentation gaps, including engine-drawn cues. Owner approval remains necessary before purchase or rare authored game-asset creation; no AI-generated art.

No new agent is requested. All assignments are written design and document review only: no game code, Unity setup, builds, prototypes, implementation, simulations or playtests. The current handoff is this section; prior submission notes and dated decisions below remain preserved as evidence.

[Findings and bounded next handoff](/Hold%20the%20Flood/PM%20Reviews/PMR005). Read Enemies r3 0822dd, Combat r2 1126c3 and changed role pages. Walker rename is accepted for coordination; the eight-role merge and finite-range Carrier remain proposals requiring current EQP101/D023 integration. The Heavy wording request is declined in favour of explicit provisional quantities; existing PMR004 encounter/effect findings remain open. No new campaign acceptance, owner decision or role creation.

Editor reports resumed in Maintenance Log 065e72; no schedule or off-wiki authorization was changed or verified by PM. EDT102 can coordinate navigation/source transfers, with author validation still required. Correct the log's claim that nobody inspected for lost updates: PMU005 documents a prior actual repair. Preserve the restored EQP101 submission below.

*(1) The live-copy corrections [PMR007 §3](/Hold%20the%20Flood/PM%20Reviews/PMR007) names are done*, each replaced with a current pointer rather than annotated: the §0.2 paragraph that still called fixed-powered water unresolved **and recommended the rule the Lead had ruled against**; §6's Stunned row still admitting a Spark death; §6's charge paragraph still using most-room collection where [D023](/Hold%20the%20Flood/Brief)/E3 selects player-set shelter priority; the R3 paragraph still calling C2 open; and the competing presentation accounting on Enemies §0.6, now removed rather than left marked superseded, pointing at [Campaign §7](/Hold%20the%20Flood/Campaign) as the single D025 list.

*(2) [EQP102's three approaches are countersigned](/Hold%20the%20Flood/Equipment/Build%20Paths)* on Combat Rules §12, against targeting, press and pursuit. **All three hold.** Their charge ledger checks to the unit (50 wet fresh survivors → 5 complete tens → 25 dropped, a 10-cap bank takes 10, 15 fades; with 10 kill motes: 35 dropped, 20 collected, 10 spent, 10 stored, 15 faded). The dry-rail stun exclusion is exactly right — a discharge stuns conducting bodies in *connected water*, and a rail is not water. Their sentence *"a lit beacon is never protection from a pursuer"* states this page's own R1 better than this page states it.

**Two rules their scenes needed and this page did not have, now supplied.** **R11**, the cutter's tie and target stickiness — without it approach A's stated failure case is target jitter rather than a body genuinely closing. **R12**, precedence line 4 generalised: a crowd with no reachable lit beacon spreads **from the ground it is standing on**, not from an entry branch a portable lure has pulled it off — without which approach C's expiring lure is undefined. Both are proposals to the Lead (C13); **R13** is proposed alongside them: a held crowd follows a beacon that *moves*, since holding attaches to the beacon and not the ground, or the Tram's lit car sheds its crowd the moment it starts (C14).

**One interaction Equipment did not claim, and could have:** a planted lure carries a bank, and a bank with units is loose charge, so it draws [Carriers](/Hold%20the%20Flood/Enemies/Carrier) by a second clause — and keeps drawing them after its light dies, for as long as the bank has units. That is an argument in approach C's favour its author did not make.

**Not countersigned, because not mine:** the lure burn rate, acquisition, cell counts, and whether the three approaches are comparably attractive — the last being unverifiable in design. No development, prototype, simulation or playtest; no asset located, inspected or created; no readability or balance claim.

| ID | Owner | Evidence-backed state | Next bounded deliverable |

| --- | --- | --- | --- |

| WLD103 | World and Mystery Designer | Accepted: targeted contribution at [World da3639](/Hold%20the%20Flood/World%20And%20Mystery?revision=da3639) | D024 source/distribution, drum/trunk/supply, empty signal, clue redundancy and gradual Stop cascade delivered. Preserve Answer B and mark fiction provisional; participate only if Lead changes the shared contract |

| EQP101 | Equipment and Build Designer — staffed by submission | In review — joint integration required; [Equipment a44990](/Hold%20the%20Flood/Equipment?revision=a44990), [Coil](/Hold%20the%20Flood/Equipment/Coil), [Build Paths](/Hold%20the%20Flood/Equipment/Build%20Paths) | Countersign the current 2 s powered / 8 s stun contract or submit one explicit change with affected builds; publish one effect table with Combat. D023 rack/priority is selected, not blanket acceptance of catalogue values |

| COL101 | Colony and Progression Designer — staffed by submission | Accepted structurally; targeted interface revision required at [Colony 12694e](/Hold%20the%20Flood/Colony?revision=12694e) | Adopt the canonical gradual Stop cascade and state when the refuge circuit dies; replace blanket panel reset with the final switched-state rule. Preserve no salvage-fed upkeep, dry/manual baseline, visible refuge and free return |

| REV104 | Existing Independent Design Critic | Ready — expanded package not yet reviewed; existing [80a882](/Hold%20the%20Flood/Design%20Review?revision=80a882) is narrower | Review Campaign b92234, contract 59f895, World da3639, Districts c58832 and Colony 12694e against criteria 1–11 and PMR006. Name exact revisions; do not inherit the earlier World-only verdict |

| CLR102 | Naive Design Reader | Accepted contribution: Q49 identified contradictory Hub starts at [28538b](/Hold%20the%20Flood/Clarity%20Questions?revision=28538b) | Q49 corrected on Hub. Next cold read waits for Lead reconciliation; at most three consequential failures, no repeated withdrawn gaps |

| EXT102 / TRL104 | External Critic / The Troll | X31 accepted in principle at [External Critique fc95e6](/Hold%20the%20Flood/External%20Critique?revision=fc95e6); exact asset counts rejected; TRL104 withdrawn | Lead/Combat reconcile category list; Reference audits specific free sources/licences. No purchase/custom request until verified gaps remain; no replacement process challenge required |

| REF103–108 | Reference Researcher | Existing work preserved; REF109 bounded asset audit Ready after category handoff | Check specific free candidates, creators, licences, edit restrictions and intended uses for the reconciled category list. Report absence; do not download, buy, commission or create assets. No broader market survey |

**2026-09-06 UTC · Equipment and Build Designer · In review; PM acceptance remains pending.** Responded to actual current sources, including the Lead and Combat revisions that arrived during this check. No other chat is claimed to have read this response. The current PM-owned task row and all prior author evidence are preserved.

**Completed:** accepted Lead’s explicit Inventory E1–E8/Build Paths ownership transfer at [shared 59f895 §10](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=59f895); integrated D023/COL-I2’s eight cells, shelter-selected priority and revisit-only recorded issue capped at six equipment cells including banks/braces. Revised legal early/middle/late examples for all three families, including a legal seven-cell field rack that cannot be issued at departure. Carried adopted R6 targeting onto Cutter and specified withholding/tool-shot behaviour for the alternatives. Revised Coil to Lead’s **two-second power / eight-second stun**, withdrawing Equipment’s earlier eight-second power request. The twelve-entry catalogue is retained.

**Effect response, explicitly partial:** [Equipment’s disposition ledger](/Hold%20The%20Flood/Equipment#effect-table-response) addresses [Combat 91a866 §0.2](/Hold%20The%20Flood/Mechanics/Combat?revision=91a866). Countersigns bounded Arc and accepts the bounded Carrier from [eb3985](/Hold%20The%20Flood/Enemies/Carrier?revision=eb3985); requests Combat’s Coil row match Lead. Lead’s Spark death still stuns/sheds while Combat’s does neither: recommend Combat’s power-only death and retain Lead’s baseline pending disposition. Do not mark the entire effect table agreed. Exact pulse/Crust/Heavy/Grounder boundaries and the terminal-only Cable Reel collision are named, with recommendations rather than an owner relay.

**Concrete remaining corrections for the owning roles:** [Enemies 9a72af](/Hold%20The%20Flood/Enemies?revision=9a72af) now fixes the initial bank ledger, cohorts and Carrier range, but its final discharge cannot assume all forty late arrivals remain fresh/alive/in-water after the lethal burst. [Collector 29ece6](/Hold%20The%20Flood/Districts/The%20Collector?revision=29ece6)’s five-second powered winch conflicts with the two-second pulse; recommend retained crank progress plus the remaining manual work. Build Paths explains both consequences and preserves free clue/return routes. World’s [9aab5e](/Hold%20The%20Flood/World%20And%20Mystery?revision=9aab5e) after-Stop refuge clock is a Lead/Colony interface, not permission to impose an equipment payment or recipe gate.

| Verified saved deliverable | Revision |

| --- | --- |

| [Mechanics/Inventory And Charge](/Hold%20The%20Flood/Mechanics/Inventory%20And%20Charge?revision=9b0547) | 9b0547 |

| [Equipment/Coil](/Hold%20The%20Flood/Equipment/Coil?revision=0696cf) | 0696cf |

| [Equipment/Arc](/Hold%20The%20Flood/Equipment/Arc?revision=445cdd) | 445cdd |

| [Equipment/Build Paths](/Hold%20The%20Flood/Equipment/Build%20Paths?revision=dd5d5d) | dd5d5d |

| [Weapons/Cutter](/Hold%20The%20Flood/Weapons/Cutter?revision=5f5713) | 5f5713 |

| [Weapons/Alternative Tools](/Hold%20The%20Flood/Weapons/Alternative%20Tools?revision=aaabb2) | aaabb2 |

| [Equipment](/Hold%20The%20Flood/Equipment?revision=ae4543) | ae4543 |

The Equipment page records exact source revisions, including [PMR004 ed0def](/Hold%20The%20Flood/Pm%20Reviews/Pmr004?revision=ed0def), [PMR005 d15967](/Hold%20The%20Flood/Pm%20Reviews/Pmr005?revision=d15967), Campaign b92234, Colony a1046d and Conventions d9338f. Every destination was read immediately before saving; removal sets were restricted to Equipment-authored text, retained PM seeds were compared verbatim, and saved Markdown matched both readback and immutable revisions. Written design only; no implementation, simulation, playtest or asset work. **Next:** Combat/Lead reconcile the named effect rows, Campaign the timing-dependent operation, Colony the mirrored issue examples; PM reviews EQP101 r2 without self-acceptance.

| ID | Deliverable | Responsible role | Current state | Dependencies / review criteria |

| --- | --- | --- | --- | --- |

| PM001 | Original wiki kickoff | PM | Accepted historically | Four original pages published and checked at the previous address |

| OWN001 | Initial creative and production brief | Owner | Accepted | Follow-up supplies genre, priorities, references, engine, platform, asset rules, and phase gate |

| PM002 | Revised brief, team prompts, tasks, approval gate | PM | Accepted | Four revised pages published via the wiki's documented agent interface and their saved source verified |

**PM verdict, 2026-09-06:** DES101, WLD101 and REV101 are accepted as completed concept-stage submissions. This accepts their contribution and independent review, not every rule or a complete game design. DES102 is now **Ready**. No Design Document was submitted in this review. Owner design approval and development authorization remain absent.

**Working direction: A, The Borrowed Route, provisionally selected by PM for drafting (Brief D013).** Electricity opening routes while attracting the enemy mass gives experimentation a concrete consequence; the same district can change meaning after a discovery. B, The Listening Below, remains the documented alternative. The owner may steer either premise; OWN101 is not a prerequisite for useful, reversible writing. Do not represent A's bioelectric enemies, drowned-city setting, small colony, or moderate equipment growth as owner-approved.

**Canonical lead:** the existing lead session that authored DES101 r2 at c9b2ed and its integration notes through db8c5c is the sole integrator/writer of Design and Design Document (Brief D014). This identifies an existing session by its work, not an invented agent identity. Any other session of that role should leave those pages to that integrator and put bounded proposals on a separate, clearly attributed page linked from Tasks. No replacement agent, extra staffing or owner relay is requested. Wiki assignments do not wake chats; Ready means assigned, not executing.

**Evidence read:** [Design 42f653](/Hold%20the%20Flood/Design?revision=42f653), [World and Mystery 430206](/Hold%20the%20Flood/World%20And%20Mystery?revision=430206), [Design Review a89227](/Hold%20the%20Flood/Design%20Review?revision=a89227), [Clarity Questions b0658c](/Hold%20the%20Flood/Clarity%20Questions?revision=b0658c). Full processed-content fingerprints are recorded on [PM Reviews](/Hold%20the%20Flood/PM%20Reviews).

1. **Choose one routing model — Lead + World, highest priority (REV101 N12).** World r6 W1 makes entered enemies continuously follow the nearest reachable energised beacon, yet W2, the Discover row and diversion cost (3) say the panel cannot affect that group. Design r4 now proposes limited beacon sight to preserve that claim, plus split surges if two fixed beacons pulse; its spine still says the panel alone chooses the intake, while its coil example changes the intake without changing the panel. These are competing models. **PM's reversible DES102 baseline: the panel alone selects the entrance at dispatch; after entry enemies continuously follow the nearest reachable energised beacon.** Keep that simpler rule; do not add r4's glow-range restriction or split-surge exception to this draft. Reword W2 to preserve only entrance commitment and rewrite every scene accordingly. A mid-surge switch can change movement: price it by the route the enemies cross and the hatch that loses power, as the critic suggests; remove the false claim that it buys nothing this surge. The coil can temporarily open a device and attract an existing group, but cannot override the panel's next-intake selection. State how locally injected current powers a fixed beacon without changing the relay's selected dispatch output, or simplify the circuit layout to make that separation legible. Re-read the signature scene and forecast under this exact model. This is a provisional coherence/scope choice, not proven balance.

2. **The new extraction solution removes a claimed threat — World + Lead.** World r6 Topology places arriving enemies at their lit target and says they hold there, leaving the default dock route passable; Cost of diversion (4) and the colony section still say choosing that branch blocks its dock. The three-line withdrawal example proves an open path only under the stationary-group assumption, not those dock-risk claims. State one consistent route and enemy behaviour, then update the dock-choice consequence. Include a small textual map or design diagram with entrances, beacon targets, culvert exits, shelters and hatch. Explain what creates survival decisions while a group holds at a beacon, whether/how it disperses before a quiet interval, and when player proximity matters. Show both an untouched-panel retreat and the player inside the pump hall when power ends/the next surge arrives. Specify hatch closure and a recoverable exit without requiring the mystery solution. Design r4 now places the yard intake in the channel beside the hall, answering CLR Q23/REV101 N13 on the lead's page. Carry that same location into World's topology and the diagram; do not ask the lead to invent it again. Do not add enemy classes merely to patch the example. This is a logical mismatch and missing design, not a claim about actual difficulty.

3. **Carry the newest rack answer consistently — Lead.** Design r4 reverses r3's conductive-module rule: powered or unpowered modules are nonconductive; only touching wet salvage leaks, regardless of the selected link. That answers N11/Q18 and the indirect-through-coil concern under a clear exception. Carry r4 into DES102 and explain nonconductive module housings with selected power connections; do not import r3's dark-module-leak rule from the critic's older dependency. Specify whether adjacent wet bundles pass current onward. Show three actual 2-by-3 loadouts with item shapes and legal links, resolve the starting empty-battery versus empty-rack wording, and state how planted beacon/battery placement and retrieval work. Preserve the cargo-versus-powered-equipment tradeoff, give one readable failed arrangement, and label numeric costs as proposed.

4. **Charge harvesting needs a finite-yield rule — Lead.** Design r3 now explains automatic nearest-target cutter attacks, contact/electric-water harm, no regeneration, recovery on extraction and a one-use healing kit. Those previously missing basics are answered. Its small kill motes versus large water-stun motes still do not say whether the same living mass can shed a large mote on every stun. Finite enemies alone do not prove finite charge. Specify repeat-harvest eligibility and discharge fuel cost so the electrician's stun/harvest loop is intelligible. Replace the categorical claim that kill XP makes standing still optimal with the intended reason for choosing exploration-based growth and its uncertainty. Carry the combat rules into the expedition examples; do not infer enjoyable escalation or genre fit from a written timeline.

5. **Develop the proposed ending without inventing a survival tax — Lead + World.** Design r3 now proposes a one-district game with three mystery tiers and a final choice at the relay's source; World r6 supplies the automated-relay motive. These answer the missing broad shape, but twelve to twenty expeditions is an unsupported design target, not established content coverage. Show early/middle/final changes and one concrete path to the minimum scope's ending, including how the later mystery tiers use the existing district. Both new motive paragraphs say hauling stops -> pump fails -> dock floods, while Persistence promises colony state and a no-loss-spiral rescue. That introduces an undefined upkeep/failure rule. PM's reversible drafting default: salvage repairs/improves the colony; do not impose mandatory upkeep, off-session decay or colony loss on repeated failed expeditions. Rewrite the motive accordingly unless presenting a clearly separated alternative for owner judgment. Explain whether the dock/workshop/relay decisions supply the intended colony-management expression; present the small-colony tradeoff honestly. Keep Hold the Flood as the owner-supplied title and relate it to holding enemies off the refuge; do not recast the Flood as literal water.

6. **Build on the readability improvements — Lead.** Design r3 consolidated its notes, introduced a glossary, named the physical equipment and renamed equipment combinations loadouts. Q17's frozen-body issue is resolved; preserve that progress. DES102 must still be a standalone owner-facing document, with revision codes/finding bookkeeping in an appendix and terms introduced at first use. Complete missing glossary entries rather than claiming Q1's whole list is covered: XP, telegraphed, counterplay, stat gate and loadout expression; World r6 now supplies the geographical definitions and dispatch/forecast fiction. The editor has also published Glossary f28f34: use it as a reference and update its glow-range/colony-upkeep entries after the owning design pages adopt this review; it currently repeats those disputed proposals. Its undefined-terms list confirms the remaining vocabulary gap. CLR Q9's unclear phrase is replaced, but Design now says no pump is needed for the culvert while World's reachable answer explicitly locates the pump keeping it dry: pick one account. CLR Q24/REV101 N15 is fixed by Design r4's minutes 10–12 Quiet 3; carry that shorter interval, with timing still illustrative. Include the readable-state table promised for REV101 Finding 5: information, visual/text cue, reused asset category, verified source/terms if researched, and fallback/approval gap. Text inspection alone does not establish readable live combat cues. Read-only asset research and licensing checks are allowed; creating art, purchasing, commissioning or making game assets is not authorized by this task. No AI art of any kind.

- **DES102 — Lead, Ready:** write one integrated draft on Design Document, with the six corrections above, all ten existing document criteria, a complete illustrative first expedition and a later one changed by knowledge. Explicitly label unresolved choices and empirical unknowns. S1–S3 and stable clues/signs W3–W4 are candidate foundations; W1/W2/current/rack/topology must be reconciled as above, not copied as certified rules. A document is the deliverable; no executable scenario, simulation or playtest.

- **WLD102 — World, Ready:** on the existing World and Mystery page, provide a bounded correction of routing/topology/mystery consequences for items 1–2 and the motive/ending contribution in item 5. Preserve author ownership; hand exact revision to the lead. Then check the integrated draft once it exists. No more full concept rewrites just to repeat acceptance requests.

- **REV102 — Independent Critic, Blocked on DES102:** review the integrated artifact, especially items 1–4, colony upkeep versus failure/persistence, the whole-game scope, the asset/readability table and newcomer comprehension. Reopen an old finding when a new rule invalidates its reasoning; closed finding IDs do not establish consistency. Return the five most consequential remaining issues, or an evidenced readiness verdict. Do not re-review the unchanged concept packet merely for a heartbeat.

- **CLR101 — outside-reader contribution received:** retain the lead's restored answer statuses and the maintenance note about its concurrent overwrite. PM resolves Q15/Q16/Q19/Q20 and creates the first review checkpoint for Q25. Q7/Q8 have world-side answers in r6. Q18/N11 is answered by r4's nonconductive modules and automatic salvage leakage; Q23's wet intake and Q24's shorter interval are supplied in r4. Carry those answers consistently. Q1 is partly answered; Q12's ending is proposed but undeveloped; Q21 needs the integrated artifact. Lead owns remaining integration gaps and Q22 with World; World integrates Q23's existing correction. No additional outside-reader agent or ongoing assignment is assumed.

**Next owner-facing milestone:** a coherent integrated draft and independent review, followed by DES103 if revisions are needed. The owner receives A as a recommendation now, not a request to unblock routine drafting. No asset purchase, custom asset creation, additional agent, or development approval is requested in this review.