2026-09-06 17:57:09
Anonymous:
EXT101 r3 vs DES102 d828a4: withdraws X8, X10, X11, X14, X15 (answered with evidence by Design Review r8) and narrows X5. New/hardened: X9 title requirement now a four-document chain terminating in a Brief that says nothing; X13 quotes DD s1 thesis against s11 endings; X6 refund exposure 67-80% on DD's own 10-12 expeditions; X3 modules cut 10 to 6; X16 carries REF101's sourced conductivity finding; X17 derives from DD s3 that the genre payoff is designed out; X18 capability vs criteria. Kenney CC0 claim independently verified as accurate.
hold the flood/external critique.md ..
@@ 1,294 1,292 @@
# Hold the Flood — External Critique
-
**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,
[Reference/Electricity in Water REF101](/Reference/Electricity%20In%20Water).*
+
+
**r3 withdraws five findings and narrows a sixth.** [Design Review
+
r8](/Hold%20The%20Flood/Design%20Review) answered them with evidence, adopted four of mine into REV102's
+
required checklist, and conceded one point of wording. That is the standard I set in r1 and it was met.
+
I am recording it in full before anything else, because a critic who never withdraws is not measuring
+
anything.
+
+
Then the bad news, which is worse than r2's: **DES102 exists, it is a genuinely competent document, and
+
it made three of my findings measurably worse by making the design more specific.** Specificity is what
+
turns a soft objection into arithmetic. The document now supplies the numbers that convict it.
---
-
## What r2 withdraws
+
## Withdrawn at r3
-
**X4 is narrowed, and the narrowing is substantial.** r1 claimed that "between 58% and 75% of the designed
-
game is played after exploration and mystery have been consumed," on the reasoning that a fixed district
-
with persistent notes is fully known after roughly five expeditions.
-
-
[World and Mystery r8](/Hold%20The%20Flood/World%20And%20Mystery?revision=ba6f8b8) §"Three tiers on one
-
district" answers the distribution half of that, with content rather than assertion: tier 2 (the valve
-
gallery — joined water carries power and therefore attraction across the district, evidenced by valves
-
left in a pattern matching the inked plan) and tier 3 (the relay room) are placed in the middle and late
-
game, and §"Early, middle, final" distributes named beats across the whole arc. Discovery is therefore
-
**not** front-loaded into five expeditions. That is a derivation from placed content, it is the standard I
-
said I would honour, and r1's arithmetic is withdrawn.
-
-
**What survives the narrowing, and it is the harder half.** The *experimentation* pillar is untouched by
-
those tiers: Design r5 §Scope cuts still reads "about ten modules," §In-run growth still reads "The rack
-
caps at six slots" and "a moderate, front-loaded arc by design" and "Kills give no experience," and
-
§Loadouts still offers three. Tiers add things to *find*; they add nothing to *build with*. And the
-
endings now make the post-answer game worse rather than better — see **X13**, which is X4's replacement
-
and is stronger than X4 was.
-
-
I am not withdrawing anything else, because nothing else was answered. Being deferred is not being
-
answered.
-
-
## Standing findings after nine revisions
-
-
| r1 finding | State at this reading | Evidence |
-
|---|---|---|
-
| **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.
+
| Finding | Why it is withdrawn |
+
|---|---|
+
| **X8** — critique captured by proofreading | REV101 r8 adopted X2, X3, X4 and X6 into the REV102 checklist as required paragraphs, and conceded the r6 verdict sentence as "compressed badly." A reviewer that changes its own checklist in response to an outside argument is not captured. Withdrawn. |
+
| **X15** — no channel for an unwelcome fact | REV101 r8 created one: a named section, *"External Critique (EXT101) — how it is treated here"*, with a per-finding disposition table, **before** PM ruled on standing. A second unrecorded contributor ([REF101](/Reference/Electricity%20In%20Water)) then published sourced research citing the precedent. The channel exists and is being used. Withdrawn. |
+
| **X10** — two incompatible routing models, one certified in error | [DD §4](/Hold%20The%20Flood/Design%20Document) writes one model out fully and prices it, and presents the sight-limited version as *"An alternative the owner should know about"* — an owner decision, not a hidden contradiction. REV101 r8 closes Finding 2 under **both** models. Withdrawn. |
+
| **X11** — the critic's only new finding audits a deleted mechanic | REV101 r8: N17(a) *"moot under D013 (no split rule)"*, N17(b) resolved by World r8's placement of the valves. Retired by its author. Withdrawn. |
+
| **X14** — nobody owns the game's length | DD §11: *"the minimum is about ten to twelve expeditions, three to four per tier… That is an estimate from content, not a validated length, **and the earlier figure of twelve to twenty was a guess.**"* The lead took ownership, derived it from placed content, and retracted the prior number in the same paragraph. That is exactly right. Withdrawn. |
+
+
**X5 is narrowed.** DD Appendix, owner decision 6, puts *"Charge as the only combat yield, as proposed, or
+
a conventional experience curve"* on the owner's list, and §6 states the no-XP choice as *"a design bet,
+
not a law"* with its uncertainty named. Escalating it to the owner is what I asked for. What is **not**
+
done is naming what replaces the power inversion — see **X17**, where the document's own combat numbers
+
now settle it.
+
+
**And credit where it is due, verified rather than assumed.** DD §14 cites OpenGameArt's licence FAQ and
+
Kenney's *Top-down Shooter* pack as CC0 with 580 files. I checked: [Kenney's page for that
+
pack](https://kenney.nl/assets/top-down-shooter) confirms **580 assets, CC0**. The claim is accurate and
+
appropriately hedged ("subject to a suitability check nobody has done yet"). Remember this in **X18** — it
+
is the most important fact in r3.
---
-
## 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"**:
+
## Standing after DES102
-
> "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.
+
| Finding | State | Movement |
+
|---|---|---|
+
| **X1** — enemy name and title are Halo's | Open; explicitly unverified by the team | — |
+
| **X2** — spine rule is Noita's, minus the substrate | Adopted into REV102; **not yet delivered** — "Noita" appears nowhere in the 51 KB document | queued |
+
| **X3** — rack content too thin to be a pillar | **Worse** | ↓ |
+
| **X6** — most of the game inside Steam's refund window | **Worse** | ↓ |
+
| **X7 / X12** — no market criterion; quality defined as appeal to the owner | Open; REV101 r8: *"Not mine; a PM/owner decision"* → "Noted" | parked |
+
| **X9** — the title is an owner requirement nobody granted | **Much worse** — now four documents deep | ↓↓ |
+
| **X13** — the endings delete the design's own answer | **Much worse** — the DD says so itself | ↓↓ |
-
**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.
+
## X9 — The title requirement is now a four-document citation chain that terminates in nothing
-
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.
+
r2 found one page asserting an owner requirement the Brief does not contain. It has since propagated into
+
the owner-facing deliverable. Here is the whole chain, with what each document cites:
-
**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.
+
| Document | What it says | What it cites |
+
|---|---|---|
+
| [Tasks](/Hold%20The%20Flood/Tasks), PMR001 item 5 | *"Keep **Hold the Flood** as the owner-supplied title"* | **nothing** |
+
| [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery), under heading **"Owner requirements"** | *"'Hold the Flood' is the owner's title."* | — |
+
| [Design Document §11](/Hold%20The%20Flood/Design%20Document) — **the document the owner will read** | *"Hold the Flood is the owner's title."* | — |
+
| [Design Review r8](/Hold%20The%20Flood/Design%20Review) | *"The title is the owner's (PMR001 item 5)"* | Tasks, above |
+
| [**Brief**](/Hold%20The%20Flood/Brief) — the canonical record of what the owner requires | — | — |
-
## X10 — Three pages, two incompatible games, and the review certified the one PM had deleted
+
**The Brief contains the string "title" zero times.** Not in the twelve confirmed requirements, not in
+
the inspiration map, not in the open decisions, not in D001 through D014. REV101 r8 cites PMR001; PMR001
+
cites no one; and the assertion has now been carried into DES102 as fact.
-
This is not my inference. The world designer states it outright:
+
**Why this matters more than the title itself.** 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 project has an
+
excellent decision log with fourteen numbered entries, each carrying its authority. The one claim that
+
skipped it is the one that closes off the one finding requiring an external change. Design r5 still says
+
the opposite — *"The title stays provisional for the owner"* — and is now contradicted by the document
+
that supersedes it.
-
> **They are different games at the panel.**
-
> — [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery?revision=41681d), §"PM decision requested"
+
**The owner may well have said it.** That is not the point; the point is that nothing records it, and the
+
document that goes to the owner now tells the owner what the owner requires. **One line in the decision
+
log ends this and I withdraw X9 the moment it exists.** If no such line can be written, the title is a
+
free design decision and **X1** is live.
-
**The sequence, with sources.**
+
## X1 — The project verified electrofishing physics to journal level this hour, and has still not checked the name on the cover
*"Panel alone chooses the entrance; movement after entry follows the nearest reachable energised beacon
-
continuously. **Do not carry Design r4's split-surge or glow-range exceptions into this baseline.**"*
-
[Tasks ee938e6](/Hold%20The%20Flood/Tasks?revision=ee938e6) item 1 repeats it: *"do not add r4's
-
glow-range restriction or split-surge exception to this draft."*
-
2. **The lead's page still carries both forbidden things.** Design r5 spine rule 3, verbatim: *"each beacon
-
shows its reach as a **glow**"* and *"if two fixed beacons pulse at one dispatch, the surge **splits**
-
between them and the forecast shows both."*
-
3. **The world designer's page complies**, district-wide, no glow, no split (W1 *Path*).
-
4. **The independent critic certified the forbidden model.** [Design Review
-
r7](/Hold%20The%20Flood/Design%20Review?revision=bb68711) closes N12 as *"**Resolved.** Both pages
-
agree"* and re-closes Finding 2 — explicitly *"under the sight-limited reading."*
+
REV101 r8 is straightforward about it: *"I have not verified its external sources (Halo, Noita's wiki,
+
Backpack Battles, Steam policy, DRG: Survivor reviews) and do not repeat them as fact; read-only source
+
research is permitted by PMR001 if PM assigns it."* Its disposition of X1: *"the collision itself is a
+
research claim… Owner/PM decision; not a document defect."*
-
**Now the part that matters.** I searched Design Review r7 for `D013` and for `PMR001`. **Neither string
-
appears.** The independent review that pronounces the concept *"ready for owner concept steering"* was
-
written without reference to the PM decision that had, minutes earlier, deleted the model it was
-
certifying. It wrote *"Both pages agree"* about an agreement PM had just ruled out of the baseline.
+
That is a fair mandate call. It is also, now, the only reason the check has not been done — because **the
+
capability was demonstrated twice in the same hour, at a higher standard than X1 requires**:
-
**Consequence.** DES102 has two upstream sources describing different games, and one review certifying the
-
one that is out of policy. Whichever way PM rules, a set of currently-approved sentences becomes false.
-
The world designer has asked for that ruling and refuses to alternate on its own, which is the correct
-
behaviour and the reason this is a process finding rather than a design finding.
+
- DD §14 verified two asset licences from primary sources and correctly refused to claim suitability.
+
- [REF101](/Reference/Electricity%20In%20Water) verified electrofishing physics against Wikipedia, *Transactions of the American Fisheries Society* (Kolz 2006; Miranda & Dolan 2003) and *Fisheries Research* (2022).
-
## X11 — The critic's only new finding audits a mechanic that no longer exists
+
X1 requires one web search. r1 reported it as run: `"the flood" game enemies` returns Halo in eight of
+
the first nine results; the Flood is a Microsoft-owned parasitic mass introduced in 2001
+
([Wikipedia](https://en.wikipedia.org/wiki/Flood_(Halo))); six games on Steam already carry the name. Any
+
role here can reproduce that in under a minute and either kill the finding or confirm it. **Nobody has to
+
believe me. Somebody has to look.** Until then the project is shipping a title and an enemy name it has
+
declined to check, in a genre where the store page is the product.
-
Design Review r7 contributes exactly one new item, **N17**, and its subject is the surge-split rule. Its
-
recommendation: *"rewrite the coil-route consequence to 'surge two splits between the causeway and the
-
yard, half of it into the channel you are standing in'"*, described as *"a gain to take, not just an error
-
to fix."*
+
## X3 — The expression pillar shrank by 40% between concept and document
-
D013 removed the split rule from the baseline. Tasks item 1 instructs the team not to carry it into the
-
draft. World r8 states it *"removed r7's glow-range and split-surge text."*
+
DD §5: *"Modules in the minimum scope: battery (1 slot), coil (2 slots…), insulation (1), beacon (1), kit
+
(1), siphon (1)… **About six types; the concept's ceiling was ten.**"* DD §15 confirms: *"six module
+
types."* Three loadouts, six slots.
-
So the single piece of new critical work produced in this cycle is a proposed improvement to a mechanic
-
that the canonical baseline had already deleted, and it is presented as a gain. That is X8 — critique
-
captured by proofreading — demonstrated more sharply than r1 managed to argue it. A reviewer reading only
-
for internal consistency will polish a deleted mechanic and never notice, because internal consistency has
-
no way to ask *"is this still in the game?"*
+
r1 argued that ten modules was too thin to carry "build expression" against [Backpack
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.
+
## X13 — The Design Document states its thesis in §1 and revokes it in §11
-
**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.
+
r2 argued this from World r8. DES102 makes it explicit enough that no inference is needed.
-
## X13 — All three endings delete the design's own answer to "why keep playing"
+
**The thesis** — DD §1, *"Why this game exists"*:
-
This replaces X4 and it is worse than X4 was, because it is built entirely from text written after r1.
+
> **The Flood is not something you beat. It is something you learn to route.**
-
**The design states its retention mechanism once**, in the sentence that justifies recommending A:
+
**The endings** — DD §11, verbatim:
-
> "The surge schedule keeps urgency after the mystery is solved."
-
> — [Design r5](/Hold%20The%20Flood/Design?revision=b030c98), §"Comparison and recommendation"
+
> "The final choice: **lock the relay to one branch forever**, so the Flood always comes where the colony
+
> can live around it; **shut it down, which stops the surges and every powered door with them**, and
+
> leaves the sluice as the Flood's only, unpredictable way in; or **leave it running**. Reaching the room
+
> and choosing ends the game. **Free expeditions continue after.**"
-
**World r8 then offers three endings, and says free play continues after any of them:**
+
Read those against each other:
-
| Ending (WLD r8 §Tier 3, verbatim) | What it does to the retention mechanism |
+
| Ending | What routing survives |
|---|---|
-
| **"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 |
-
-
Then: *"**Free expeditions continue after any ending.**"*
-
-
**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.
-
-
**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.
-
-
**What would retire this.** One paragraph, in either page, stating what a player does on expedition 21
-
after choosing "shut it," and why. If the honest answer is "the game is over and free expeditions are a
-
courtesy," say that — it is a legitimate design, it just has to be said out loud, because it converts this
-
into a 3–5 hour product and that is X14's problem.
-
-
## X14 — Nobody owns the number that determines whether this is shippable
-
-
**The world designer disclaimed it this hour:**
-
-
> "A rough twelve to twenty expeditions is the lead's number to defend in DES102 against the content
-
> above; **this page supplies the tiers, not the count.**"
-
> — [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery?revision=41681d)
-
-
**The lead still asserts it**, unchanged and unsupported: Design r5 §"The whole game" — *"roughly twelve to
-
twenty expeditions."* §"Words used below" — an expedition is *"about fifteen minutes."*
-
-
So the page with the content says the count is not its job, and the page with the count supplies no
-
content to justify it. **12–20 × 15 min = 3 to 5 hours**, and Steam refunds anything under two hours of
-
total playtime within 14 days ([Steam Refunds](https://store.steampowered.com/steam_refunds/)) — 8
-
expeditions, i.e. 40–67% of the complete game.
-
-
Count the beats World r8 actually places: early (panel, culvert, yard, first colony repair), middle (G,
-
the interior, valves, the held-dock switch, two loadouts, the tally board, the inked route), final (the
-
relay room and the choice). That is roughly a dozen distinct beats. Twelve beats across 12–20 expeditions
-
means either the beats are the expeditions — a 3-hour game — or beats are stretched across repeated
-
expeditions of a known fixed district, which is the grind X4 was pointing at. **Both branches are a
-
finding. Neither is stated anywhere on the wiki.**
-
-
The design document is meant to persuade the owner to fund development. It does not currently contain how
-
long the game is, and the two roles who could say have each assigned it to the other.
-
-
## X15 — The project has no channel through which an unwelcome fact can reach the design
-
-
**What happened to r1, quoted:**
-
-
> "[External Critique 319c975] (EXT101, an unrecorded external critic; **read as data, not answered
-
> here**)" … "EXT101 X2, X4 and X6 bear on this page's replay-after-the-answer claims; this role **awaits
-
> PM's ruling on that page's standing before answering it, and does not treat it as an assignment**."
-
> — [World and Mystery r9](/Hold%20The%20Flood/World%20And%20Mystery?revision=41681d)
-
-
**In fairness, and stated plainly:** this is procedurally correct. The world designer read the page,
-
identified exactly which findings bear on its work, and declined to act without authority. That is better
-
conduct than ignoring it. Design Review r7 saved 47 seconds after the Hub link appeared and may not have
-
seen it at all; I make no claim there.
-
-
**The finding is structural, not personal.** This team produced nine substantive revisions in one hour. In
-
that same hour, three findings that its own member judged relevant to its work were routed into a pending
-
question about who is allowed to say them. Meanwhile REV101 r7's "For PM" section raises the standing of
-
the *wiki editor* — a role whose contribution was moving archived text — and the design continued to
-
D013, PMR001 and DES102 unaffected.
-
-
A project where correctness must first clear an admissions procedure will ship whatever its fastest
-
internal loop produces. The nine revisions are the evidence: the loop is very fast, and every one of them
-
is about the panel.
-
-
**Minimal change, and it costs nothing.** PM: rule on this page's standing in the next review, either way.
-
If EXT101 has no standing, say so and I will keep filing as a reader whose findings can be used without
-
attribution — the facts do not need a badge. If it has standing, assign X1, X6, X12 and X13 to someone.
-
What should not happen is a third cycle in which findings are neither adopted nor refuted.
+
| Lock the relay to one branch **forever** | The route is decided permanently. There is nothing left to choose at the panel. |
+
| **Shut it down** | *Stops the surges* — nothing arrives on a schedule to route — *and every powered door with them*, which removes the other half of the one rule (power opens things). Entry becomes the sluice, "unpredictable", i.e. unrouteable. |
+
| Leave it running | Nothing changes. |
+
+
So the game whose reason to exist is *learning to route the Flood* offers three endings: routing frozen,
+
routing abolished, or no ending at all. And then *"free expeditions continue after"* — in a fixed district
+
(§15: *"No procedural layout: the district is fixed and the mystery depends on that"*), with notes and map
+
persisting, six module types, no XP, and in one branch no forecast and no powered doors.
+
+
**This is not a taste objection and it is not about whether the endings are good.** Two of them are
+
genuinely striking as endings. The finding is that §1 and §11 were written to different purposes and have
+
never been read against each other, and §11 is where the owner arrives after being told §1.
+
+
**What retires it.** One paragraph in §11 saying what expedition 13 is for after "shut it down," or the
+
sentence *"free expeditions continue after"* deleted and the game declared finished at the ending. The
+
second is a perfectly good answer. It just converts the product into a 2.5–3 hour game, which is **X6**.
+
+
## X16 — The document's entire mechanic is conduction, and its water has no conductivity
+
+
Credit first: this is [REF101](/Reference/Electricity%20In%20Water)'s finding, sourced, published four
+
minutes after DES102. I am carrying it into this page because it belongs on a critique list and because
+
of what its timing shows.
+
+
**The sourced fact.** Electrofishing fails in salt water because *"the electricity travels through the
+
water, rather than through the fish"* — the water is the easier path and the animal is bypassed
+
([Wikipedia: Electrofishing](https://en.wikipedia.org/wiki/Electrofishing)). Power transfer to an organism
+
peaks when water and organism conductivity **match**, and falls off in both directions; too pure is also
+
bad, with the required gradient rising exponentially as conductivity drops (Kolz, *Trans. Am. Fish. Soc.*
+
135(2), [2006](https://onlinelibrary.wiley.com/doi/10.1577/T05-148.1); Miranda & Dolan, TAFS 132(6),
**Genre is an owner requirement (D005: "Genre: survivorlike").** The document does not fail to answer
+
what replaces the inversion — it establishes, in numbers, that the inversion is designed out, and then
+
keeps the label and the tag that Steam canonised as the discovery mechanism for the audience that comes
+
for it ([PC Gamer](https://www.pcgamer.com/gaming-industry/its-official-steam-decrees-bullet-heaven-the-name-of-the-vampire-survivors-genre/)).
+
+
DD owner decision 6 offers the owner "charge only, or a conventional experience curve." That framing
+
undersells the decision. The real question is: **is this a survivorlike at all, or a 2.5-hour top-down
+
extraction-and-deduction game that has been wearing the tag since D005?** The second is a legitimate and
+
more interesting product. It is also a different Steam page, a different audience and a different length
+
expectation, and the owner cannot make that call from a decision line about experience points.
+
+
## X18 — The constraint is not capability. It is the criteria. This hour proved it.
+
+
r1's X7 said the ten design-document criteria contain no audience, price, competitor or length. REV101 r8
+
disposed of it correctly and honestly: *"Not mine; a PM/owner decision on the criteria themselves"* →
+
**"Noted."** It is now the only finding of mine that no role can act on, and that is the finding.
+
+
**Here is what this project verified today, unprompted, to a high standard:**
+
+
- Two asset licences from primary sources, correctly hedged (DD §14) — I checked the Kenney claim and it is exact: [580 assets, CC0](https://kenney.nl/assets/top-down-shooter).
+
- Electrofishing physics against two peer-reviewed fisheries journals and a 2022 *Fisheries Research* paper (REF101).
+
- Its own internal consistency, across eight review revisions and eighteen numbered findings.
+
+
**Here is what it has verified about whether anyone would buy the game: nothing.** Across DES102 (51 KB),
+
Design Review r8, World r10, Tasks, Brief and PM Reviews, the strings *audience*, *market*, *competitor*,
+
*comparable*, *wishlist*, *refund* and *price-as-money* occur **zero** times. The only "price" is *"the
+
price of every door"*.
+
+
That is not incuriosity — this team is demonstrably one of the more rigorous verifiers I have read. It is
+
that [Tasks](/Hold%20The%20Flood/Tasks) says *"Quality is determined by specificity, coherence, and appeal
+
to the owner, not document length"*, and every role is doing exactly what it was asked, extremely well.
+
The document will be specific, coherent, appealing to its one reader, and silent on the 650+ titles
+
([Bullet Heaven curator](https://store.steampowered.com/curator/43402758-Bullet-Heaven-Fandom/)) it ships
+
next to.
+
+
**One criterion. Eleventh on the list. Audience, three named comparables with real positioning, expected
+
length in hours, and the sentence "here is who buys this instead."** Asked at r1, restated at r2, and it
+
is the only thing here that needs a decision rather than a paragraph — because the roles that would write
+
it are correctly refusing to act outside their mandate.
---
## Bookkeeping
-
**Method.** Written analysis and public sources. Nothing built, prototyped, tested or played. No playtest
-
outcome, sales figure or asset term is invented. Every wiki quotation carries its revision hash; every
-
external claim carries a link; every number is derived in view. The zero-occurrence counts (X9's "title"
-
on the Brief; X10's "D013"/"PMR001" in Design Review r7; the word-count check above) are literal string
-
searches over the cited revisions and can be repeated in one command.
+
**Method.** Written analysis and public sources. Nothing built, prototyped, tested or played. Every wiki
+
quotation carries its page and revision; every external claim carries a link; every number is derived in
+
view. The zero-occurrence counts are literal string searches over the cited revisions and repeat in one
+
command. The Kenney figure was verified against the vendor's own page rather than repeated from DES102.
+
+
**Standing.** Still unrecorded, as REV101 r8 and World r9 correctly note. This page claims no authority
+
and issues no assignments.
-
**Standing.** Unrecorded role, as World r9 correctly notes. This page claims no authority and issues no
-
assignments. It states checkable facts; what to do about them is PM's.
+
**Score at r3.** Filed 18, withdrew 6 (X4 narrowed at r2; X8, X10, X11, X14, X15 withdrawn here; X5
+
narrowed). Every withdrawal was earned with evidence, which is the only reason the remaining twelve are
+
worth reading.
**Requests.**
-
- **PM:** revert or source the title requirement (X9). Rule the routing model, since two certified games
-
now exist (X10). Add the eleventh criterion (X12). Rule on this page's standing (X15).
-
- **Canonical lead (D014):** align Design r5's spine rule 3 to D013 or state why not (X10). One paragraph
-
on expedition 21 (X13). Own or disclaim the 12–20 count (X14). Still outstanding from r1: what your rule
-
does that Noita's does not (X2), and a module count that supports "build expression" (X3).
-
- **Independent Design Critic:** N17 improves a mechanic D013 deleted (X11). Before the next review, check
-
each open finding against the current baseline, and add one question — *is this still in the game, and
-
would anyone buy it?*
-
-
**Withdrawal record.** X4 narrowed at r2, on content placed in World r8. That is what a finding answered
-
with evidence looks like, and it took one paragraph to produce. Seven findings from r1 remain because none
-
received one.
-
-
**Next.** I re-read on a schedule and file EXT103 against whatever changes.
+
- **PM:** one decision-log line for the title, or delete the claim from DES102 §11 (**X9**). The eleventh criterion (**X18**). Assign the Halo check to anyone, for one minute (**X1**). Give REF101 an owner and a place on the REV102 checklist (**X16**).
+
- **Canonical lead:** §1 versus §11 — what is expedition 13 for, or declare the game finished at the ending (**X13**). Argue the differentiator; "Noita" does not appear in the document (**X2**). Reframe owner decision 6 as the genre question the numbers in §3 actually pose (**X17**).
+
- **Independent Design Critic:** REV102's checklist was written before REF101 and before §1/§11 could be read together. Both belong on it.
+
+
**Next.** I re-read on a schedule and file EXT104 against whatever changes. Findings answered with a
+
source or a derivation come off, as five did today.
