Commit a28870

2026-09-06 21:57:29 Anonymous: PMR006: review expanded campaign integration and assign bounded reconciliation
/dev/null .. hold the flood/pm reviews/pmr006.md
@@ 0,0 1,70 @@
+ # PMR006 — expanded campaign integration review
+
+ **Completed 2026-09-06 · PM · Design-only review.** This review compares actual current sources with PMR005 and the broader PMR004 handoff. It reads the expanded Campaign, shared power contract, World response, Campaign/District revisions, Combat response, Colony response, external critique and clarity question at the exact revisions listed below. It does not infer progress from timestamps, page counts or status prose.
+
+ ## Verdict
+
+ The project has reached its first **coherent expanded-campaign skeleton**. Seven external districts plus the refuge now share one provisional machinery/mystery explanation; the Collector and Head-Works have concrete cross-district consequences; the colony has expedition-facing choices; Combat has corrected its two illustrative encounters and bounded the Carrier. This is substantial progress and the relevant domain contributions are accepted as delivered work.
+
+ The overall design is still **In review — integration changes required**. It is not ready for owner design approval and development remains closed. Four rule interfaces still describe different games, the owner-facing ending text is stale, the asset burden is internally inconsistent and unsourced, and the independent critic has not reviewed this expanded revision.
+
+ ## What is accepted
+
+ 1. **WLD103 targeted response is accepted at World r22.** World now uses Answer A, distinguishes drum, trunk permission, enemy supply and fixed power, explains the empty dispatch signal, supplies redundant essential clues, and gives Stop a legible district-by-district cascade. This accepts the contribution, not the fiction as owner-approved or the complete campaign as coherent.
+
+ 2. **CAM101's PMR004 correction is accepted as a contribution.** Districts r4, Collector r4 and Head-Works r4 correct the dark-bank routing error, spend charge locally, state the Collector buffer and level thresholds, preserve physical access gates, and reduce the finale to Stop / Keep / Leave. Their baseline path now identifies 34 expeditions and 492 minutes (8.2 hours) of authored expedition beats, with eight optional expeditions / 120 minutes separate.
+
+ That number is a **content-backed drafting hypothesis**, not measured playtime and not a finding that the owner-requested scale is sufficient. Dock overhead is an unmeasured 25–35% assumption; deaths, retries and hauling are excluded. The Exchange remains outline-level and some Lead-authored districts still need attributed transfer. The smallest useful next step is to deepen the weakest district and reconcile the full baseline path—not inflate time through resource prices or repeat hauling.
+
+ 3. **COL101's structural direction is accepted.** One active support assembly, free baseline departure/return, the eight-cell issue contract, reversible shelter choices, visible refuge changes and no forced defence fit D023. Costs remain hypotheses. A narrow Stop-timing revision is still required.
+
+ 4. **CMB101's PMR005 corrections are credited.** Walker naming, a bounded 12 m Carrier, corrected encounter bookkeeping, explicit provisional Heavy quantities and the withdrawal of the vague Heavy wording and incorrect 19-kill argument are useful corrections. Combat is not accepted as a common rule source until it matches the current shared contract and Equipment.
+
+ ## Blocking integration contradictions
+
+ 1. **Coil duration:** Power and Attraction r3 makes the water energised window **2 seconds** and stun **8 seconds**. Combat r4 and the current Equipment/Coil proposal use **8 seconds** for the powered water. Consequence: insulation, collection timing and Encounter A have different costs depending on which page the reader follows. **Correction:** Lead owns the current 2-second canonical ruling; Combat and Equipment must either countersign it everywhere or submit one explicit change request with all affected examples. No page may silently keep 8 seconds.
+
+ 2. **Spark effect:** the shared contract says a Spark killed in water energises it and stuns conducting bodies, while Combat/Enemies/Spark says the two-second hazard does not stun or damage organisms. Consequence: the same enemy can either disrupt a whole wet crowd or only threaten the player. **Correction:** Lead and Combat choose one row, then update the contract, effect table, Spark page and affected encounters together.
+
+ 3. **Ordinary state persistence:** the shared state table says panel positions and Grounder-disabled runs persist as left; Colony's inherited seed still says field state and panel state reset. Consequence: players cannot know whether a route prepared on one expedition remains prepared on the next. **Correction:** Lead distinguishes temporary combat/electrical effects from ordinary switched state and authored permanent commitments; Colony then mirrors that rule instead of using a blanket reset sentence.
+
+ 4. **Stop cadence at the refuge:** the shared contract and World now use a gradual one-district-per-expedition cascade, while Colony r2 proceeds on immediate loss of powered colony services. Consequence: the timing of advanced tooling, forecast and pumped berth access is undefined. **Correction:** Colony adopts the canonical gradual cascade, explicitly states when the refuge circuit dies, and preserves its useful rejection of salvage-fed upkeep plus the dry landing/manual bench baseline.
+
+ 5. **Ending copy:** Head-Works now uses Stop / Keep / Leave, but Campaign's pitch and owner-decision section still say “set it slower.” Consequence: the short owner path advertises an option the domain author withdrew. **Correction:** Lead updates those two passages and checks the linked outcome wording; do not invent a fourth position.
+
+ ## Content, presentation and review gates
+
+ - **Coverage:** Seven districts is the current drafting baseline, not an owner-approved production commitment. The 8.2-hour baseline plus separately listed optional material is a better answer than the withdrawn 3–4 hour claim, but remains a paper estimate. Lead and Campaign should complete the Exchange and confirm that every imported district beat belongs in one baseline ledger before asking the owner whether the scale feels ambitious enough.
+ - **Asset strategy — EXT X31 accepted in principle, counts not accepted.** Campaign says eight enemy silhouettes; Combat/Enemies alternates between six and eight; External Critique says three. A production decision cannot be based on all three. Lead and Combat must identify the actual presentation categories and which are reuse, pose, engine-drawn cue, licensed edit, new asset or cut candidate. Reference Researcher then performs a bounded free-source/licence audit. Only remaining verified gaps should become an owner purchase/custom-asset decision. No asset has been approved, acquired or commissioned.
+ - **Independent review:** REV104 remains Ready. The critic must read Campaign b92234, Power and Attraction 59f895, World da3639, Districts c58832 and Colony 12694e, test the written rules and campaign proposition, and identify the exact revision reviewed. Existing World-section critique is not review of this package.
+ - **Navigation — Q49 accepted.** The Hub correctly supplies a short owner route but also retains an old “start here / 91 minutes” instruction for the obsolete one-district GDD. PM will remove the contradictory instruction and retain the GDD as a legacy mechanical source with a scope warning.
+
+ ## Bounded handoff
+
+ - **DES104 / Lead:** reconcile the five rule/copy contradictions above; ensure the short Campaign pitch, shared contract and topic pages agree; do not recopy catalogues. Treat 2-second Coil power as canonical unless proposing a single explicit replacement.
+ - **CAM102 / Campaign:** deepen the Exchange to the same standard as the three detailed districts, reconcile the 34-expedition baseline with Lead-owned beats and coordinate attributed transfer. Keep optional visits and unmeasured overhead separate.
+ - **CMB101 + EQP101:** publish one countersigned effect table matching the current contract, resolve Spark, and reconcile the six/eight-role presentation count. Preserve corrected encounter arithmetic.
+ - **COL101:** update only the Stop/persistence interface and source ledger; keep no mandatory upkeep, manual refuge access and free baseline return.
+ - **REF109 / Reference:** after Lead/Combat supply one category list, check specific free candidates, creators, licences, adaptation restrictions and intended uses. Report gaps; do not download, buy or create assets.
+ - **REV104 / Independent Critic:** review the exact expanded package after or alongside these corrections; do not infer execution from this assignment.
+
+ No additional agent is needed for this pass. The current specialists cover the open work. No code, build, prototype, implementation, simulation, playtest, game art, audio, purchase or custom asset was authorized or produced.
+
+ ## Processed artifact snapshots
+
+ | Artifact | Verified revision | Source SHA-256 |
+ | --- | --- | --- |
+ | [Campaign](/Hold%20The%20Flood/Campaign?revision=b92234) | b92234 | `11a835b2c34becf5f5ae04875d0ca2ed6147e45349ee5621de9b3850ff3ec2e4` |
+ | [Power and Attraction](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=59f895) | 59f895 | `6c82f0d8599113573005bb0f448bd63a9b397f3fb4717d3fc2c84e98f7a5b4c7` |
+ | [World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery?revision=da3639) | da3639 | `cfb3fd6d2b5a0482c313d77d35b3d8eb3486c4043758022106cbfccb41a112c5` |
+ | [Districts](/Hold%20The%20Flood/Districts?revision=c58832) | c58832 | `0f7fbd9c71ed10fbfc74f1e0fbd340d0497afd99c3cae93b31c7b3d828d19a22` |
+ | [Collector](/Hold%20The%20Flood/Districts/The%20Collector?revision=75c09e) | 75c09e | `2b587b1502cf4722f42719a7e61918f92842e5851df80887bc9c0cb0692cafd4` |
+ | [Head-Works](/Hold%20The%20Flood/Districts/The%20Head-Works?revision=706ce6) | 706ce6 | `1174b5c0faf9dea37870d80175f150e593c4a1f8d0666a1c96553dcc1cb5b686` |
+ | [Combat](/Hold%20The%20Flood/Mechanics/Combat?revision=91a866) | 91a866 | `37f9e474c2617c04b4aa3be257f61f06f1eb060856bf1232d2f6052f3b408b92` |
+ | [Enemies](/Hold%20The%20Flood/Enemies?revision=9a72af) | 9a72af | `d95a00c8045088cc60907bec23476de4ad55aa502a202064c5418ae131da1cac` |
+ | [Colony](/Hold%20The%20Flood/Colony?revision=12694e) | 12694e | `413665bf68e2ea7a44f4724011c1a0cae91ea3ea80f861caa29fd64e45aaae62` |
+ | [External Critique](/Hold%20The%20Flood/External%20Critique?revision=fc95e6) | fc95e6 | `098c02c0335e5d041d0fedd37bb6be5d411891708a32f2d5096a586939eff284` |
+ | [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions?revision=28538b) | 28538b | `50f5282792133f576bf5144cfd95a2b3640625aa3a1b48942f295c927b8ecdd0` |
+ | [Design Review](/Hold%20The%20Flood/Design%20Review?revision=80a882) | 80a882 | unchanged independent review; expanded package not reviewed |
+
+ Supporting role/entity pages were read where needed to verify the contradictions. Unchanged equipment pages remain governed by PMR004/PMR005 and are not newly accepted. This report makes design-document judgments only; feel, balance, readability, performance and enjoyment remain unverified.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9