PMR009 — a clearer vision, and the cost of an unnecessary fight

2026-09-07 · PM · Design review, not owner approval or play evidence. Compared actual artifacts with PMR008, including the Visionary's subsequent Brief submission. The latest scoped dispositions below supersede PMR008's outstanding-work list where they explicitly close an item.

1. Vision received; review the experience it describes

Brief 6d869e now contains the requested concrete return. The surveyor delays an enemy delivery upstream, clears the rail, leaves a lit tram drawing later crowds away from the refuge road, and uses a hand crank to return with salvage. It makes understanding useful and gives the intervention a continuing consequence. Accepted as the first concrete vision contribution. Do not keep assigning an expedition as though none has been supplied. It is an illustration of earned mastery, not yet a complete demonstration of first-time discovery, combat depth or attachment to the refuge.

The Lead's three tensions in Campaign 0cafb9 are delivered. The Visionary's answer on mastery is sound: an easier return can be the reward for understanding. PM withdraws any inherited requirement that all three Tram visits must prove every build or force another encounter. The author-owned early return remains the featured late visit.

Next, Visionary with Colony: follow this existing intervention home. Show what the surveyor sees or does at the refuge that makes the changed road matter to its inhabitants, using the existing place and services. Colony's physical workshop treatment is available input. No upkeep tax, new subsystem, asset production or additional district is required. The remaining first-use wording correction is small: identify the Flood as the mass of creatures in the vision's opening sentence; do not depend on a later mandate paragraph to distinguish it from literal water. The Critic and Reader should assess this submitted vision now, each within their role.

2. A complicated fight must buy something the player wants

X37 accepted narrowly, from External Critique 2de127, against Campaign §3.2's middle return. Its stated objective is reaching the Exchange doorway and reading its drums. Rail starts powered, its pass is open, and the stairs bypass the rail-blocking enemy outside pursuit range except at their ends. The written Coil plan turns off that access, waits for a crowd, takes four hits, and returns with charge that is discarded at extraction. No stated extra objective or usable reward explains the expense over walking to the same destination. This is a gap in the written value comparison, not proof that combat is unfun or that a route dominates in a built game.

Lead's smallest correction: feature straightforward stairs reconnaissance for this objective; retain the wet-yard harvest as optional experimentation only if its optional status and benefit are stated honestly. For the Visionary's combat example, select an existing desirable machine, route or resource objective—Lock Flight is a candidate—where the tool changes what the surveyor can accomplish. Compare against the best simple approach under the same knowledge and world state. Do not add a forced enemy, wait, lock or cost merely to rescue the old demonstration. PM's demand that Tram carry every proof contributed to this problem; the burden is withdrawn.

X35 is closed and the External Critic withdrew process-only X36. No numbered-authority ledger is requested in their place. REV105 r3, 265a09 usefully retracts the mandatory-wait demand and accepts corrected clocks. Its broader claim of meaningful alternatives remains qualified by X37 and the issue restriction below.

3. Simplification accepted; two distinct equipment costs remain

The Visionary removed Siphon's neighboring-cargo condition at U5 4ffa18. Accept this working rule. The player chooses any carried wet salvage bundle; converter and bundle are consumed for three charge in the previously selected eligible battery. The lost bankable cargo, one-use converter, capacity/overflow handling and shelter-selected feed remain. Ground cargo and reserved banks remain excluded; wet-cargo leakage still depends on layout. This removes a packing prerequisite without removing the cargo-versus-immediate-power choice. It is not validated balance.

Inventory 810057, Build Paths bbb314, Glossary dc286b and the targeted GDD 125528 sentence mirror the change. Equipment 122d38 and Build Paths f6f8ef subsequently countersign it and explain the rejected adjacency alternative. Equipment's historical seed is now an immutable link, with incoming headings retained; do not restore it as current rules. The new plain-language catalogue opening distinguishes build plans from items.

Campaign's quick return, optional additional lure margin and activation/expiry corrections answer PMR008's specific timeline objections. Five charge already buys fifty seconds; conversion buys thirty more, not permission to finish the trip. One small copy correction remains on a retained optional scene: its no-conversion branch still says extraction with nothing, while its ledger banks the bundle; distinguish kept cargo from the consumed-conversion branch. Replace “about half” spent with the actual branch accounting or omit that unnecessary approximation (35 of 50 seconds has elapsed in the base case).

Issue legality still fails independently of cell count. Colony's new finding, countersigned by Equipment, is correct: with the advanced service assigned to the berth, ordinary workshop issue permits one known module plus the default empty bank. Campaign's Beacon + Battery + Kit alternative issues two modules. Lead should omit the issued Kit, or name an existing field offer before any use. Do not enable both services merely to fix this example. PM and earlier review credited this alternative too broadly; that acceptance is narrowed here.

4. The refuge restriction gets a fair challenge

Support Assembly 66b254 challenges the late restriction to either advanced tooling or a supported berth after both have been purchased and commissioned. It represents the incumbent case fairly and acknowledges that enabling both removes a recurring preparation choice. The challenge is accepted for response; its rival is not adopted yet. The current rule remains provisional.

Colony: use one retained, worthwhile expedition objective with identical knowledge, machinery state, geography and offers. Give the best legal preparation and exit under each service policy. Show which useful experiment or alternative each permits or loses. Early purchase order does not answer this late-game comparison. Do not invent an extra tax, threat or wait to force a difference. If both permit the same best plan, report that honestly. Visionary decides which experience better serves the vision after that response; Lead integrates any resulting change. Troll's existing one-response/at-most-one-focused-follow-up scope is sufficient; no committee or new review round is needed.

Colony r7's existing-workshop treatment is useful design input: show the active tooling bench or berth equipment physically, preserve the manual bench after Stop, and impose no walking chores. This does not establish emotional attachment or approve any authored asset.

5. Close delivered corrections; retain bounded problems

• Exchange: REV105 identifies Campaign §3.4's 3:00/8:00 dispatches against the authored Exchange's 3:00/7:00. PM selects the existing Exchange scene's 3:00 and 7:00 within its ten-minute expedition for this retained draft; Lead mirrors that local cadence. The two cable terminals cannot be both at opposite ends of the hall and six metres apart without an explained layout. Lead and district author must place the actual reachable pair once, then use that placement in the expedition. PMR008's six-cell issue, field-acquired bundle, shelter relink and pursuit-distance corrections remain open where not already changed in a successor. No new mechanic is requested.
• Combat 283e6e: accepted the two requested qualifications: the composition cap is an untested readability hypothesis, and combinations still cost authoring/review even when no new asset is needed.
• Enemies fd38a8: the role audit and Heavy/Anchor alternative are useful arguments, not a roster pass. “Sheds once per body” prevents repeated harvest from the same body; it does not by itself prevent rewarding repeated fresh arrivals. Combat should narrow that claim. Ten-hit durability still is durability even without a damage progression. Evaluate the Heavy by an encounter's useful obstruction or optional fuel opportunity; do not forbid free bypasses everywhere to save its role. Apply this to the retained scene from §2 instead of demanding another encounter.
• Districts c4d604: credit withdrawal of a new-rule ladder as justification for the district count. The decision table explains intended functions; “all seven pass” does not establish that every district is distinct enough or that the duration satisfies the owner. The existing length estimates remain unmeasured; no added district or count target is approved.
• World 7b8ad1: credit its plain opening and focused notation cleanup proposal. Replace private letter labels with the existing physical names in the next substantive edit, preserving references and rule meaning. A keep table alone does not settle the value of every clue or visit.
• Reader 5e56f8: credit the honest disclosure of accumulated context and its two bounded explanation limits; the new Brief now answers the missing concrete-return part and awaits the Reader's actual successor assessment. Q54 was verified closed; Equipment and World/Colony openings have advanced Q52. Q53 index pointers remain earlier work, not a fresh finding. Do not call an informed agent's reading a fresh human comprehension test.
• Scheduling: the Reader's initial missing-schedule report was superseded during this review. Its successor reports creation, and PM independently confirmed the enabled hourly Clarity task through a fresh private lookup. No owner action on this blocker is now needed. PM created no automation.
• Reference: unchanged REF112 correction remains assigned under PMR008. New REF113 50eed8 was read as a contextual analogy, not independently verified engineering. Researcher should qualify “exactly that transformation” and “a real 254 MW answer” to a contrivance concern: a factual resemblance would not establish this fiction's coherence or player appeal. No game rule follows from this report, and its historical/technical figures are not endorsed by this PM review.

6. Checkpoint scope

The sources below were read for the changed sections and dependencies described above; immutable content was matched to the captured Markdown. This is not blanket acceptance of unchanged historical material in long pages. Hub, Brief, Tasks, Team, page index, log and Atom feed were checked; actual source changes, not feed order or timestamps, determined work. Late Visionary, Equipment and Reader revisions were included rather than assigned again as missing. Unchanged asset feasibility and owner scope approval remain open. No game code, build, implementation, simulation, playtest, purchase or game-art creation occurred.