Commit ed0def
2026-09-06 20:40:01 Anonymous: PMR004: review expanded campaign and four domain submissions; rule conflicts and provisional decisions| /dev/null .. hold the flood/pm reviews/pmr004.md | |
| @@ 0,0 1,71 @@ | |
| + | # Hold the Flood — PMR004: expanded campaign integration review |
| + | |
| + | **2026-09-06 · PM · Substantive submissions received; integrated acceptance withheld.** |
| + | [Tasks](/Hold%20the%20Flood/Tasks) · [Brief / decisions](/Hold%20the%20Flood/Brief) · [Revision checkpoint](/Hold%20the%20Flood/PM%20Reviews). |
| + | |
| + | ## Outcome and drafting decisions |
| + | |
| + | The expansion is now actual design work, not just page structure. All four proposed roles have submitted: Campaign/Districts, Combat/Enemies, Equipment/Builds, Colony/Progression. Their contributions establish staffing for wiki coordination; they do not prove any chat's schedule or receipt of a handoff. Existing Lead remains sole integrator. No replacement or additional agent is needed for the next assignment. |
| + | |
| + | **D022 — Draft seven external districts plus the refuge, without a forced refuge-defence expedition.** Accept Campaign's seven-area recommendation provisionally: Pumping, Lock Flight, Tram Incline, Exchange, Collector, Tidal Barrier, Head-Works. It preserves different terrain, machinery, travel and discovery problems without counting the home base as an extra district. This revises PM's eight-area hypothesis, not an owner-approved count or production budget. A justified eighth remains possible. Reject CAM101 §2's absolute claim that sharing a consequence-table cell makes two districts reskins: topology, encounters, discoveries and build choices can distinguish areas using the same machinery. Salt Pans currently lacks enough justification; that is a deferral, not a permanent ban. |
| + | |
| + | **D023 — Use EQP101's eight-cell rack from the outset and shelter-selected pickup priority for the next integrated draft.** Prefer this over six-to-nine capacity progression: the complete Coil/Arc combination leaves room for cargo or a countermeasure, while a portable beacon plus bank consumes that margin. Priority lets players deliberately ready an action instead of accidentally splitting charge. Retain capacity, one-to-one links, no field rewiring and committed Arc fuel. Adopt COL101's one reusable assembly / one active advanced service as the colony drafting baseline, with one-time refits and free baseline departure/return. Accept EQP's six-issued-cell cap for recorded racks on revisits only; first-visit packages must leave discoveries meaningful. These are reversible design judgments, not demonstrated balance; prices and electrical-effect proposals are not thereby approved. |
| + | |
| + | **D024 — Develop World's Answer A (the continuing harvesting machinery) as the provisional mystery for the next draft.** It connects the central combat resource, city infrastructure and final cost without requiring another character/presence system. Preserve B as a documented alternative; neither setting nor ending is owner-approved. For dispatch, adopt the local-drum AND trunk-permit interpretation: both authorize a dispatch signal; actual arrivals also require enemy supply. Fixed power is a separate state. Lead and World must publish the complete source/distribution/Stop consequence rather than treating this ruling as the missing explanation. |
| + | |
| + | These decisions authorize writing only. Unity/Steam and all design-only/asset restrictions remain unchanged. Numerical tuning, enjoyment, readability at crowd density and performance remain unverified. |
| + | |
| + | ## 1. Campaign machinery must share one contract |
| + | |
| + | Sources: [Campaign 9d3590](/Hold%20the%20Flood/Campaign?revision=9d3590), [World 7699de](/Hold%20the%20Flood/World%20And%20Mystery?revision=7699de), [Power and Attraction 69024c](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction?revision=69024c), [REV104 80a882](/Hold%20the%20Flood/Design%20Review?revision=80a882). |
| + | |
| + | Credit the independent critic's five specific campaign-interface findings. **REV104-2 is resolved in shared contract 69024c:** charge never leaves a district *with the player*; machinery may transfer it. Do not reopen that wording defect. REV104-1/3/4 still need the adopted AND condition, empty-dispatch signal convention and fixed-power source embodied consistently in the rules. REV104-5 is partly addressed by Campaign §3.4's loss of forecasts; that cost is not proof the routing bank is balanced. |
| + | |
| + | **Dark dispatch does not mean unroutable enemies.** [Districts acb797 §4](/Hold%20the%20Flood/Districts?revision=acb797) says unannounced trickles spread and cannot be routed around; Collector §7 makes the same inference. Lit beacons still exist under D013/D016. Fix to unannounced arrivals that still obey ordinary post-entry targeting. Retargeting starts immediately, but bodies take time to leave; no instant clearing of occupied ground. |
| + | |
| + | Lead + World: one compact table must distinguish fixed power, hydraulic flow, trunk permission, local timing, enemy supply and observed warning. State source, connection, what changes it, and what survives exit. Include Stop's powered-door/pump losses and the baseline gravity/dry return. Head-Works must not generalize that flowing water cannot conduct: identify the actual dry breaks and power feeds. Reconcile starvation's water-level consequence between Collector and Head-Works. Essential clues and return cannot quietly require purchased services or a new unexplained generator. |
| + | |
| + | ## 2. Combat and equipment proposals cannot both be canonical yet |
| + | |
| + | Sources: [Combat 5edba0](/Hold%20the%20Flood/Mechanics/Combat?revision=5edba0), [Enemies 0a3fc1](/Hold%20the%20Flood/Enemies?revision=0a3fc1), [Equipment a44990](/Hold%20the%20Flood/Equipment?revision=a44990), [Inventory 73eb77](/Hold%20the%20Flood/Mechanics/Inventory%20And%20Charge?revision=73eb77). |
| + | |
| + | The new roles offer actual choices: displacement versus killing, narrow penetration versus general coverage, charge-carrying threats, interrupted lures and resistant bodies. Keep that progress. The following are **written-rule contradictions**, not claims about game feel: |
| + | |
| + | - **R3 versus Coil:** Combat proposes one second of powered water; Equipment proposes eight. Stun duration is a separate quantity. **R10 versus Arc:** whole connected-water propagation conflicts with Equipment's capped nearby body-to-body hits, Cutter host and no world-power injection. Combat and Equipment must jointly submit one effect table for fixed power, Coil, Arc and Spark: power duration, stun, damage, propagation, refresh, charge yield and readable state. My recommendation is the bounded Arc model for this draft because it preserves spatial limits; R10 remains an alternative, not an implied property of electricity. Do not adopt every effect at once. Lead resolves any remaining disagreement in that same submission. |
| + | - **Encounter A:** the Yard was powered at 7:30. Expiry of the 8:25 Coil pulse cannot make its still-fixed-powered channel inert at 8:26. Correct the remaining supply and its consequence for collection/Insulation. |
| + | - **Encounter B:** two full banks start at twenty; Coil spends ten and is refilled; Arc spends ten. That leaves a full Coil bank, not two empty banks. Carriers therefore cannot stop chasing because charge is supposedly exhausted. Separate bodies already stunned at 12:25 from those still arriving until 12:30 before declaring every target spent or zero kill yield. Show these cohorts and both bank states in the corrected scene. |
| + | - **Grounder:** darkening one beacon does not necessarily make its followers spread; first evaluate another reachable lit beacon. **Crust:** confusing it with a spent Drifter is not harmless: one resists the stun that the other still receives, and unshed kill yield must match the charge rule. Separate conductivity and remaining-yield cues. **Spark:** ordinary insulation already protects against energized-water injury; it is not a newly invented secondary job. Specify whether its death effect only powers water, also stuns, or damages other bodies; the open question cannot silently supply a chain-kill rule. |
| + | |
| + | Campaign and Combat also need one disposition of the flow-carried floater used by Lock Flight. Do not silently delete that district interaction by replacing the four-role roster with six names. Assess pursuit safety against accumulated/merged crowds, not only a first surge. The owner's brief does not ban numerical growth, other statuses or bosses; a compact initial grammar is a scoped proposal, not proof those alternatives are inherently bad. |
| + | |
| + | ## 3. Finish the district consequences; do not promise hours yet |
| + | |
| + | Sources: [Districts acb797](/Hold%20the%20Flood/Districts?revision=acb797), [Collector 40f2b5](/Hold%20the%20Flood/Districts/The%20Collector?revision=40f2b5), [Head-Works 6bf2a7](/Hold%20the%20Flood/Districts/The%20Head-Works?revision=6bf2a7). |
| + | |
| + | Collector's hold/release tradeoff and Head-Works' city-wide consequence are useful expansions. Smallest corrections: |
| + | |
| + | 1. Collector §§4/9 advertises coming for charge and leaving with charge, but §5 correctly forbids carrying it out. Replace the expedition reward with a named **local** charge expenditure and resulting discovery/cargo/route benefit. Explain how an empty starting bank reaches its first discharge; do not make this a preparation farm for a later district. Repack its example against D023. |
| + | 2. Collector §6 closes the outfall yet exempts later surges. Specify the targeted district, finite buffer or bypass, when the one-surge benefit is consumed, and the forecast shown. Tie the actual quiet window to that district's schedule. Reconcile the claimed loss of the lower gantry after one level increase with §2's two-level threshold. |
| + | 3. Head-Works' freely adjustable Keep appears able to reproduce Slow while retaining reversibility. Merge Slow into that outcome or supply a distinct benefit/cost. Explain the interaction commitment versus the claim that every choice is a single interaction. No compulsory return for upkeep unless a new rule is explicitly proposed and justified. |
| + | 4. Distinguish physical/discovery access from notebook unlock flags. A route requiring a recorded note is not purely player-knowledge gating. Where prior understanding is supposed to suffice, permit the known action without compulsory clue collection; keep redundant essential evidence and honest optional branches. |
| + | |
| + | CAM101's separated first visits/revisits/optional estimates are more useful than multiplying district count. **The proposed duration remains unaccepted:** required-return totals contain optional branches/deferrals; Pumping visit assumptions differ from the Lead; overhead and death/retry exclusions need consistent accounting. Submit one baseline path with concrete discovery beats, genuinely required returns, optional branches, and separate uncertain overhead. No extra hours through hauling quotas. Seven districts and many documents do not by themselves establish the substantial campaign the owner wants. |
| + | |
| + | ## 4. Colony, ownership and next handoff |
| + | |
| + | [COL101 a1046d](/Hold%20the%20Flood/Colony?revision=a1046d) supplies a campaign-spanning loop with three competing services, reversible preparation, failure recovery and explicit persistence. The one-time dock refit is preferable to repeatedly charging for experimentation. Adopt the structural choices in D023, not every cost or claim of equal attractiveness. |
| + | |
| + | Colony + Campaign: distinguish the optional Tram summit berth from the baseline held dock; show its canal prerequisite and extraction tradeoff. Equipment: integrate COL-I2's inspection/recipe and revisit-only recorded-rack policy. World: ensure comparative observations use information the player could already obtain and never sell essential mystery access. Show one lasting, visible refuge consequence of the investment beyond a different loadout menu. No NPC simulation or new asset authorization is implied. |
| + | |
| + | **DES104 next submission:** integrate the chosen rules and district consequences, not all prose. Provide a short owner narrative covering a first trip, a changed middle-game return, a later build choice and the campaign payoff; link authoritative domain pages. Domain authors validate and transfer their material; Lead records which definitions now own the rule. The Wiki Editor reports being paused at its owner's request in Maintenance Log. Do not resume that role; Lead/domain authors cover necessary transfers and PM covers navigation meanwhile. Administrator health checks remain separate. |
| + | |
| + | REV104's delivered section critique is accepted as a contribution, not approval of the whole campaign. The awaited Campaign now exists: the critic can review it immediately with this report, and verify later corrections only at actual revisions. The older REV103 review reports closure; PM's scoped inspection credits the current ledger/ending/header corrections without claiming a new full audit of GDD r15. New EQP rules require new examples, not reuse of the previous ledger's acceptance. |
| + | |
| + | ## Coordination dispositions and review limits |
| + | |
| + | - **TRL104:** the owner explicitly requested more content and districts. Price expectations, refusal of finite endings or a replay-hour target were not supplied. Proceed with a larger finite authored campaign plus optional replay as a reversible planning assumption; no owner clarification is necessary to continue drafting. |
| + | - **EXT X30:** correct D018's stale content-expansion status under D019; the owner's preference does not rehabilitate the invalid market-length inference. **X26:** AI-written design prose is authorized work, not permission to ship generated text, code, audio or other production assets. Defer any otherwise unspecified production policy to an actual later approval request; no current art exception. |
| + | - **Q45:** Hub now offers the Campaign owner summary and Build Paths as the short read; the long GDD is a linked rule source, not compulsory owner reading. **Q46:** GDD r15 already labels its inherited short scope. Mid-rollout missing-page findings Q47/X28/X29 are withdrawn; no replacement issue is requested. |
| + | - New research is received, not independently audited here or accepted as asset/legal/market guidance. Page length is not a quality benchmark. Checkpoint records the exact scoped review; unseen research details and unreviewed legacy passages remain outside it. |
| + | |
| + | **Acceptance gate:** coherent expanded design, meaningful choices and mysteries, honest content coverage and asset burden, followed by owner assessment. This report is design critique and coordination; no build, prototype, simulation, playtest, asset production, purchase or validated playtime is claimed. |