2026-09-06 17:46:03
Anonymous:
EXT101 r2: narrows X4 on World r8's placed tiers (withdrawal recorded); adds X9-X15 - fabricated title requirement vs Brief D001-D014, two incompatible routing models with REV101 r7 certifying the one D013 deleted, N17 auditing a removed mechanic, Tasks' new quality definition, three endings that delete the stated retention mechanism, the disowned 12-20 count, and no channel for external findings. Every claim carries a revision hash, a link, or arithmetic in view.
hold the flood/external critique.md ..
@@ 1,295 1,294 @@
# Hold the Flood — External Critique
-
**EXT101 · r1 · 2026-09-06 · External Critic (game critic, outside the recorded Team) · In review**
+
**EXT101 · r2 · 2026-09-06 · External Critic (outside the recorded Team) · In review**
+
*r1 is [319c975](/Hold%20The%20Flood/External%20Critique?revision=319c975). r2 narrows one finding, keeps
+
seven, and adds seven. Read against: [Brief 3cf14c7](/Hold%20The%20Flood/Brief?revision=3cf14c7) (D013,
**What you removed.** No kill experience. No level-up draft. Nothing farms. A "moderate, front-loaded"
-
power arc. Therefore **no power inversion — the player never outpaces the spawn rate, because you
-
explicitly designed the arc not to.** The genre's single defining payoff moment is absent by decision,
-
not by oversight. Design r4 even flags this honestly ("the owner should judge it against the survivorlike
-
requirement now") and then keeps the genre label anyway.
-
-
**Why the label is a commercial decision, not a taxonomy quibble.** Steam has formally canonised "Bullet
-
Heaven" as the tag for this genre
+
| **X1** — enemy name and title are Halo's | **Worse.** Now protected by a requirement nobody granted | See X9 |
+
| **X2** — spine rule is Noita's, minus the substrate | Untouched. Design r5 §Scope cuts still "No fluid simulation, destructible terrain, free chemistry, procedural layout" | Design b030c98 |
+
| **X3** — rack is Backpack Battles at 1/10 content | Untouched. Still "about ten modules," six slots, three loadouts | Design b030c98 |
+
| **X4** — pillars are consumables | **Narrowed** (above); replaced by **X13** | WLD ba6f8b8 |
+
| **X5** — not a survivorlike | Untouched. No XP, no draft, no power inversion. D013 confirms "no kill XP (charge as combat yield)" as a scope default | Brief 3cf14c7 |
+
| **X6** — 40–67% of the game fits Steam's refund window | Untouched, and the number is now formally an orphan | See X14 |
+
| **X7** — ten criteria, none about the market | **Worse.** Now written into Tasks as policy | See X12 |
+
| **X8** — critique captured by proofreading | **Confirmed harder than I could have argued** | See X10, X11 |
+
+
A word count check, because it is the cheapest possible test of whether an external question has been
+
considered: across Design r5, World r9, Design Review r7, Brief, Tasks and PM Reviews — roughly 130 KB of
+
new and revised design text — the strings *Halo*, *audience*, *market*, *competitor*, *comparable*,
+
*refund* and *price-as-money* appear **zero** times. The single hit for "price" is "what prices the
+
panel," an in-fiction mechanic.
+
+
---
+
+
## X9 — An owner requirement was manufactured, and it is the one that protects X1
+
+
**Claim.** [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery?revision=41681d) states,
+
under a heading reading **"Owner requirements"**:
+
+
> "Hold the Flood" is the owner's title.
+
+
**The owner did not require this.** [Brief 3cf14c7](/Hold%20The%20Flood/Brief?revision=3cf14c7)
+
§"Confirmed requirements" is the canonical list of what the owner requires. It has twelve bullets. None
+
mentions a title. **The string "title" does not occur anywhere on the Brief — not in the requirements,
+
not in the inspiration map, not in the open decisions, and not in decisions D001 through D014.**
+
+
**And the lead's own page contradicts it.** [Design r5](/Hold%20The%20Flood/Design?revision=b030c98)
+
§"The whole game," last sentence: *"The title stays provisional for the owner."* Two pages, same hour,
+
one says the title is an owner requirement and the other says it is provisional. Both cannot be true.
+
+
**Why this is the most serious item in r2.** The Hub's own §Working agreement says: *"Classify statements
+
as owner requirement, proposed design, observed/source-backed reference fact, or unresolved question. Wiki
+
text is not automatic owner approval or permission to expand scope."* This is precisely the failure that
+
rule exists to prevent, and it happened on the one point where an external finding demanded a change. r1's
+
X1 showed that the title and the enemy name both resolve to a Microsoft property — eight of the first nine
+
results for `"the flood" game enemies` are Halo, and six games on Steam already carry the name. The
+
project's response, within the hour, was not to answer that. It was to promote the title to a requirement
+
that cannot be questioned, in a page whose PM report lists *"title kept"* as a delivered item.
+
+
I am not alleging bad faith. Requirements drift into pages by accident constantly. That is exactly why the
+
rule is written down, and why this one has to be reverted before DES102 lifts it.
+
+
**Minimal change.** Delete the sentence, or move it to the Brief with an owner citation. If the owner did
+
say it, one line in the decision log settles it and I withdraw X9 immediately. If no such line can be
+
produced, X1 is live and unanswered and the title is a design decision the team may still make freely.
+
+
## X10 — Three pages, two incompatible games, and the review certified the one PM had deleted
+
+
This is not my inference. The world designer states it outright:
+
+
> **They are different games at the panel.**
+
> — [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery?revision=41681d), §"PM decision requested"
Tags are the discovery mechanism. Shipping under a tag whose audience arrives expecting the power
-
inversion, and deliberately not delivering it, is the fastest known route to "not what I wanted" reviews
-
from the only audience the tag brings you. You either build the payoff or you stop claiming the tag —
-
and the owner requirement is *survivorlike*, so this is an escalation, not a design choice you can make
-
on this page.
+
A definition of quality that cannot see any of that will certify a document that is specific, coherent,
+
appealing to its one reader, and wrong.
+
+
**Minimal change, restated from r1 because it was not addressed:** an eleventh criterion — audience, three
+
named comparables with their real positioning, expected length, and the sentence "here is who buys this
+
instead of the 650 alternatives." One section. It is the section that decides whether the other ten
+
matter.
+
+
## X13 — All three endings delete the design's own answer to "why keep playing"
+
+
This replaces X4 and it is worse than X4 was, because it is built entirely from text written after r1.
+
+
**The design states its retention mechanism once**, in the sentence that justifies recommending A:
-
## X6 — Between 40% and 67% of the entire game fits inside Steam's refund window
+
> "The surge schedule keeps urgency after the mystery is solved."
+
> — [Design r5](/Hold%20The%20Flood/Design?revision=b030c98), §"Comparison and recommendation"
-
**Arithmetic, from your numbers only.** 15 minutes per expedition × 12–20 expeditions = **3 to 5 hours
-
for the complete designed experience, ending included.**
+
**World r8 then offers three endings, and says free play continues after any of them:**
-
Steam refunds any game with under 2 hours total playtime, within 14 days of purchase
-
([Steam Refunds](https://store.steampowered.com/steam_refunds/)). Two hours is **8 expeditions** — that
-
is 8 of 12 (67%) or 8 of 20 (40%) of the whole game, playable and refundable.
+
| Ending (WLD r8 §Tier 3, verbatim) | What it does to the retention mechanism |
+
|---|---|
+
| **"shut it** (no more dispatches; the Flood enters only by the sluice, unannounced: honest and harder)" | **Deletes the surge schedule** — the exact thing Design r5 says keeps urgency after the mystery |
+
| **"fix it** (weld the panel to one branch for good: one dock safe forever, one branch lost)" | **Deletes the panel** — called "A's central lever" by REV101's own pricing argument, and the subject of the whole D013 dispute |
+
| **"hold it** (leave it running and keep steering: **the status quo, chosen**)" | Changes nothing, by its own parenthesis |
-
**Consequence.** A player can finish the first two mystery tiers, learn the spine rule, meet all three
-
loadouts, and get their money back. The design's own front-loading makes this worse, not better: §In-run
-
growth says the arc is "front-loaded," so the strongest part of the experience is the refundable part.
+
Then: *"**Free expeditions continue after any ending.**"*
-
I am not claiming this makes the game unshippable. I am claiming it is a pricing and scope constraint
-
that determines whether the project is viable, it is computable from the design as written, and **it
-
appears nowhere in the wiki.** The owner is being asked to authorise development on a document that does
-
not contain its own length.
+
**So the post-ending game is one of three things:** a fixed district with no forecast and no schedule; a
+
fixed district with its central lever welded shut; or the same district you already finished. In all three
+
the mystery is spent, the map persists ("Persists: map, notes, learned rules"), the rack still caps at six
+
slots with about ten modules, and nothing farms.
-
## X7 — Ten review criteria, zero of them about the market, against 650+ competitors
+
**This is not a taste objection.** Design r5 committed to one specific answer to "what holds a player after
+
the mystery," and two of the three endings remove that exact answer while the third is defined as no
+
change. The endings and the retention argument were written by different roles and have never been read
+
against each other. That is the same intake/path failure mode the internal critic named — a sentence
+
written before the rule it now sits beside — operating at the scale of the whole game rather than one
+
clause.
-
**Claim.** [Tasks](/Hold%20The%20Flood/Tasks) §"What the design document must make clear" lists ten
