*Previous revisions in [history](/Hold%20The%20Flood/External%20Critique/history).
-
Targets re-read at save: **[Brief](/Hold%20The%20Flood/Brief)**, **[Team](/Hold%20The%20Flood/Team)**,
-
**[Campaign](/Hold%20The%20Flood/Campaign) (DES105 r3, page r8)**, and the arc's four pages.
-
Rollout check: the Hub and Design Review were saving at 11:39–11:41; the Brief settled at 11:05, Team and
-
Campaign earlier. Nothing I cite is in flight, and I flag nothing on the Hub.*
+
**EXT102 r17 · 2026-09-07 · External Game Critic · In review; PM owns acceptance.** Resumed product review: one consequential finding. Supersedes [r16 / 7b657e](/Hold%20The%20Flood/External%20Critique?revision=7b657e); earlier reviews remain in [history](/Hold%20The%20Flood/External%20Critique/history).
-
**X35 is closed, and closed better than I proposed.** One new finding, **X36**, on the same pattern the
-
project already accepted once and fixed with D019.
+
## The strongest fair version
-
---
+
You venture out from a refuge into a drowned city whose machinery controls the enemy Flood. Survive long enough to understand a machine, use its lights, water and power to redirect danger, and leave it in a state that changes your next journey. Discovering that the city harvests the very creatures threatening you makes those practical interventions into a question about what your home should keep running.
-
## X35 — withdrawn, and the fix is better than the one I suggested
+
The likely player enjoys crowd survival that puts investigation and planning under pressure: towing enemies with a tram lamp, redirecting them away from an exit, packing for an intervention, and returning to a place they have made easier. That is my audience judgment, consistent with [Campaign 0cafb9, owner opening](/Hold%20The%20Flood/Campaign?revision=0cafb9#read-this-first-one-page-for-the-owner), not evidence of audience demand.
-
I asked for the stale clause to be restated with the current numbers. The lead removed the number instead:
+
**The most consequential weakness is that the featured middle expedition spends heavily on combat without showing what that expenditure buys over an already available walk.** If that is representative, knowledge makes the investigation efficient while the build system becomes an optional detour. The activities then coexist more convincingly than they reinforce one another.
-
> "**Scope:** the Districts page's current ledger, quoted in section 8 with its caveats, a hypothesis and
-
> not a measurement."
+
**Product verdict: promising, worth continuing in written design, but the current expedition does not yet make a convincing case for the whole promised combination.** The vision is available at [Brief 0fff74](/Hold%20The%20Flood/Brief?revision=0fff74#game-vision). A concrete expedition is also available: [Campaign 0cafb9 §3.2](/Hold%20The%20Flood/Campaign?revision=0cafb9) describes the Tram across three visits. The Visionary-specific expedition requested on [Tasks 1c38ca](/Hold%20The%20Flood/Tasks?revision=1c38ca) remains pending; this review evaluates the existing Lead scene, not an invented successor.
-
That cannot go stale again, because it no longer carries a figure to go stale. Fixed-string check across
-
Campaign r8: *"thirty-five expeditions"* — **0**; *"eight and a half hours"* — **0**.
+
## X37 — the middle visit has a costly build, but no demonstrated reason to choose its fight
-
## X36 — two owner actions today are recorded in prose and in neither the decision log
+
**1. Claim and source.** [Campaign 0cafb9 §3.2, changed return and vision-test table](/Hold%20The%20Flood/Campaign?revision=0cafb9) presents the wet-yard Coil approach versus a lure/berth approach as meaningful preparation for the same investigation. [Build Paths 6d6d1d, EQP102 approach B](/Hold%20The%20Flood/Equipment/Build%20Paths?revision=6d6d1d) describes its purchase as a local control window. This finding concerns that scene's product evidence, not the usefulness of Coil everywhere.
-
**What the owner did**, from the [Brief](/Hold%20The%20Flood/Brief)'s own text:
+
**2. Why it could disappoint.** A player attracted by experiments that change how they explore needs a reason to choose the demanding experiment. Here an informed player appears able to accomplish the stated investigation with less equipment and exposure by simply starting up the stairs. A player who follows the elaborate plan instead may reasonably feel that preparation bought extra work rather than agency.
-
> "**2026-09-07.** The owner **rejected the latest pitch as barely understandable** and raised a deeper
-
> concern: disconnected mechanics and terminology do not communicate one coherent game… The owner has now
-
> **created The Visionary, explicitly empowered to challenge any agent's design decisions and change or
-
> remove mechanics** that do not support a clear identity and vision."
+
**3. Evidence, reasoning and counterargument.** Documented facts: the changed visit starts on Rail, which opens the pass; the stairs bypass the rail Heavy and sit outside the incline road's pursuit range except at their ends. The first surge is due at 3:00. The proposed plan switches away from Rail, waits for arrivals, earns and spends a full battery in the wet yard, takes four hits over the trip, returns to Rail for the ascent, and ultimately loses the refilled charge at extraction. The same summit evidence and stores are the stated destination. [Shared rules 5322f4 §6](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=5322f4) say entered crowds do not persist between expeditions.
-
Both are recorded — in Brief prose, and the role and mandate on [Team](/Hold%20The%20Flood/Team) under
-
*"PMU008 — owner added The Visionary… Owner-confirmed staffing and mandate."* Neither is hidden.
+
My inference: compare this with walking up the initially available stairs. No initial stair obstruction, extra reward, lasting intervention or subsequent charge expenditure is specified that favours the fight. This is an incomplete design argument, not a logical impossibility or a tested optimal route; exact traversal safety remains unvalidated.
-
**Neither is in the decision log.** Fixed-string check over the 26 decision rows, D001–D026: rows
The strongest counterargument is that choosing to harvest can teach a reusable rule, and a player may enjoy the fight even when it is inefficient. Build Paths also explicitly permits abandoning the paid plan for free machinery; that freedom is good. However, the changed-return player already owns a recorded Coil setup, the example gives the resulting charge no further job, and neither the evidence nor the Siphon offer requires the fight. Optional experimentation may be enjoyable; this scene has not established that it supports a scarce tooling investment or renews the expedition for an informed player. Future player evidence could establish intrinsic combat appeal, but none exists in this design-only phase.
-
**And the log has the pattern for both, twice:**
+
**4. Smallest change and sacrifice.** Remove the voluntary wet-yard detour from the featured middle return and let the stated reconnaissance use the available stairs. Retain harvesting as an optional experiment. Demonstrate the costly build where an existing objective actually benefits from it—for example, the Lock Flight's powered-door problem in [Campaign 0cafb9 §3.1](/Hold%20The%20Flood/Campaign?revision=0cafb9)—instead of making the Tram carry every system's proof. This sacrifices the claim that these three Tram visits alone demonstrate three worthwhile build strategies. It preserves the free route, earned ease and equipment rules; no compulsory wait or equipment key is proposed.
-
| Precedent | What it records |
-
|---|---|
-
| **D015** | *"Record five owner-added contributors: Naive Design Reader, Wiki Editor, External Critic, Reference Researcher, The Troll"* — authority **Owner follow-up** |
**5. What would change my verdict.** A revised written expedition in which the simple route and the combat investment each buy a concrete, independently desirable outcome for the same informed player would answer this finding: access, useful cargo, a persistent intervention or credible recovery margin tied to an actual hazard. An already specified benefit or route constraint I have missed would narrow or withdraw it immediately. If the game instead deliberately treats combat mainly as an avoidable investigation hazard, that can be a coherent product too, but its audience promise should reflect that choice. Neither additional catalogue entries nor agreement between reviewers would answer the point.
-
D015 is the row that seated me. D019 exists because of **X28**, which was this same finding about the
-
expansion, and PM accepted it. A sixth owner-added role now exists with **more authority than the five
-
D015 records** — the power to remove any mechanic — and the owner has rejected a pitch, which is the same
-
class of act as rejecting a scope. The log carries neither.
+
## What should be retained, and why choose this over alternatives?
-
**Why it is not bookkeeping.** The Visionary can change or remove mechanics that other roles' decisions
-
established, and several of those decisions are in this log — D013, D016, D022, D023, D024, D026. When a
-
mechanic is removed under the vision mandate, the row that authorised it will need to point at the
-
authority that overrode it, and that authority currently has no number to point at.
+
Keep the tram lamp's moving crowd, the distinction between a call and an actual arrival, persistent machine settings, free essential observations and the later quick return. In [Campaign 0cafb9](/Hold%20The%20Flood/Campaign?revision=0cafb9), the later visit no longer forces a wait until the second surge: understanding the Collector's withheld supply lets the player set the tram's standing state and leave early with cargo. The Siphon is now honestly optional margin. Those are substantive improvements, not objections to reopen.
-
**Minimal change: two rows**, following D015 and D019 exactly — one recording the owner's creation of The
-
Visionary and its mandate, one recording the pitch rejection and the coherence concern, both with **Owner
-
follow-up** authority and PMU008 as the source.
+
For comparison, [Noita's official description](https://noitagame.com/) offers environmental experimentation and crafted spells; [Deep Rock Galactic: Survivor's developer page](https://www.fundaygames.dk/deep-rock-galactic-survivor) offers horde combat, mining and upgrades (checked 2026-09-07). My comparative judgment: Hold the Flood's strongest reason to choose it is a legible, persistent city that the player learns to operate, with the mystery changing the use of that same machinery. It need not surpass those games in mechanic count or unprecedented ideas. The finite campaign can earn its value through consequential situations; district totals and estimated hours do not establish that value, and I make no price, sales or completion-time claim.
-
**What I am not claiming.** Not that the Visionary's authority is wrong or too broad — that is the owner's
-
to grant and they have granted it. Not that anything is concealed; the Brief's prose is prominent and the
-
Team mandate is explicit. Not a comment on the pitch itself: the owner's comprehension complaint belongs to
-
the Naive Design Reader and now to the Visionary, and I am not duplicating either.
+
After the harvest explanation is understood, the surprise itself is spent. Persistent consequences and applying known rules to another machine can still be satisfying. [World 7b8ad1, WLD104](/Hold%20The%20Flood/World%20And%20Mystery?revision=7b8ad1) supplies local questions and changed-world returns, and the revised late Tram provides one concrete payoff. That supports further design work; it does not yet establish sustained interest across the larger campaign. I would retain the finite ending rather than demand endless replay.
-
---
+
## Disposition and review checkpoint
-
## Checked and clean: the arc, across four pages
+
X35 remains closed. **X36 is withdrawn:** the owner's rejection and Visionary mandate are already explicit on [Brief 0fff74](/Hold%20The%20Flood/Brief?revision=0fff74) and [Team 890a96](/Hold%20The%20Flood/Team?revision=890a96). Missing numbered rows do not materially change this product verdict. This narrows my remit; it does not claim PM added the rows. Earlier closed findings remain closed.
-
The shared-rules paragraph changed the arc's burst from about twenty seconds to about ten, which is the
-
number my old **X22** turned on. I checked all four places it is stated:
+
Sources read: the revision-linked design sources above, [PMR008 37fd94](/Hold%20The%20Flood/Pm%20Reviews/Pmr008?revision=37fd94), [Tasks 1c38ca](/Hold%20The%20Flood/Tasks?revision=1c38ca), and [Wiki Conventions 86a8db](/Wiki%20Conventions?revision=86a8db). Discovered through the index and log; source text checked against immutable revisions. Written analysis only: no game code, prototype, simulation, playtest or asset creation.
-
| Page | States |
-
|---|---|
-
| Campaign §1 | *"the arc drains one over ten seconds, body to body"* |
-
| [Power and Attraction](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction) (the contract) | *"drains a full linked battery over about ten seconds, one burst per battery"* |
-
| [Mechanics/Inventory and Charge](/Hold%20The%20Flood/Mechanics/Inventory%20And%20Charge) | *"Arc uses one full battery for about ten seconds and cannot extend that burst by collecting"* |
-
| [Equipment/Arc](/Hold%20The%20Flood/Equipment/Arc) | *"draining ten to zero over its fixed duration… That battery accepts no pickups during the burst"* |
-
-
**Consistent, and it retires X22's residue by design rather than by wording.** Ten units over ten seconds
-
is **1.0 unit/second**; the cutter yields **0.67 unit/second** at one unit per kill, three hits per kill,
-
two hits a second. The cutter alone can no longer fund the burst, and *"accepts no pickups during the
-
burst"* closes the collection route entirely. The bound is now the surge, as §6 always claimed it was.
-
-
## Bookkeeping
-
-
**Method.** Written analysis and the project's own pages. Nothing built, prototyped, tested or played. All
-
counts fixed-string.
-
-
**One method error of mine, caught before publication.** Searching the decision log for `vision` returned
-
six rows, and I nearly reported the Visionary as recorded. All six matches were the word **pro·vision·al**.
-
The fixed-string count is zero. That is the third substring false positive I have caught on this page and
-
the reason every count above says "fixed-string": my grep habits have cost me two published errors and I
-
am not adding a third.
-
-
**Running score: filed 36, retracted or withdrawn 35, one live (X36).**
-
-
**My own published errors remain ten** — four caught by PM, one by the conventions page, five by me.
-
-
**Requests.** PM: two decision rows (**X36**). Nothing else outstanding from this page.
-
-
**Next.** Hourly.
+
**Handoff:** Lead/Visionary: answer or narrow X37 with the actual route and outcome, or adopt the smaller demonstration above. PM owns disposition and acceptance. Re-review only a material response, a changed vision/expedition, or new relevant evidence; no-change passes require no edit or owner notification.
