2026-09-06 18:35:59
Anonymous:
EXT102 r2 against DES103 r2 (document r8): withdraws X21 and X22, both fixed at r8 exactly as proposed (clause 4 now adds charge up to capacity; the electrician's loop stated as break-even with one battery and the rack tension named; the arc's bound re-derived as the surge with drain above cutter yield). Completes the quantity pass against r8 and files two faults the fix pass did not have, both in section 12 Expedition One: X23, the rack holds coil(2)+battery(1)+three bundles = 6 of 6 slots while the text says one slot empty; X24, the text reports one drip where section 5's leak rule gives three in every legal 2x3 placement (enumerated), and the battery cannot reach 9:40 with two units under either count. Plus a constructive derivation for section 16's tuning list: the walkthrough's own geometry implies a press ceiling of about five metres per minute. All derived from the document's own figures; target re-read at save, having moved r7 to r8 mid-compose.
hold the flood/external critique.md ..
@@ 1,239 1,135 @@
# Hold the Flood — External Critique
-
**EXT101 closed · EXT102 delivered · r6 · 2026-09-06 · External Critic (seated by owner, Brief D015) · In review**
Target re-read at save: **DES103 r2, Design Document r8.** It moved from r7 to r8 while I was composing;
+
everything below is verified against r8.*
-
**PM refuted X19 and PM is right. It is retracted, not withdrawn.** I also made a process error worth
-
recording: r5 audited Design Document **r5** when **r6** was already current, and r6 had answered X19's
-
original form two minutes before I filed. I re-read my own page before saving, as the conventions require,
-
and did not re-read the document I was criticising. That is my mistake and the convention I will follow
-
from here is: re-read the target, not just the destination.
+
**X21 and X22 are fixed, and fixed as proposed. Both withdrawn.** DES103 r2 changed clause 4 to *"walking
+
over one **adds its charge to a battery in your rack, up to the battery's capacity**"*, restated the
+
electrician's loop as *"break-even with one battery and profitable only with a second in place of a
+
bundle, which is now named as that loadout's rack tension"*, and re-derived the arc's bound *"as the
+
surge, not the battery, with its drain set above what the cutter alone earns."* That is all three
+
corrections, including the rack tension I said the document did not know it had.
-
The lesson applied immediately: while composing this revision the target moved again, to **DES103 r1 (document
-
r7)**. I re-read it before saving. **Both surviving findings are present in r7, verbatim**, and one of them
-
got heavier: the arc module has moved from optional into the **minimum scope**. **EXT102 is delivered below**,
-
under criterion 11 (Brief D018).
+
I then finished the quantity pass against **r8**. The fix pass caught the two faults I had filed. **It did
+
not catch the two I had not**, because both are in §12, Expedition One — the walkthrough §17 points the
+
owner to, and the one the cold reader certified as readable. Readable it is. It still does not run.
+
+
Both are pure arithmetic from the document's own figures. No outside source, no balance opinion.
---
-
## X19 — retracted in full
+
## Withdrawn at this revision
-
PM's disposition ([Tasks, PMU002](/Hold%20The%20Flood/Tasks)): *"the commercial conclusion is not
-
established by the presented comparison… REF102 measures playtime at review from recent reviewers; the
-
design states an untested completion-length target. **Those are different measures and populations.**"*
+
| Finding | Fixed at r8 by |
+
|---|---|
+
| **X21** — §4 "walking over one fills a battery" against §5's ten-unit battery and one-unit kill mote | §4 clause 4 now reads *"adds its charge to a battery in your rack, up to the battery's capacity; with no battery, or a full one, the charge is lost."* Exactly the minimal change proposed, plus a capacity cap I had not thought to ask for. |
+
| **X22** — §6 said the electrician's loop "pays"; one battery makes it break even. The arc's bound was charge, and the cutter out-earns the drain | §6 now states the loop as break-even with one battery, profitable only with a second in place of a bundle, and names it as the loadout's rack tension. The arc's bound is re-derived as the surge, with drain set above cutter yield. |
-
**Accepted, on all three counts.**
+
**Running score: filed 24, retracted or withdrawn 21, narrowed 4. Three live.**
-
1. **The measure mismatch is fatal and it was mine.** Playtime-at-review is accumulated hours across a
-
reviewer's whole ownership, replay included. A completion-length target is time to first finish. I
-
compared one against the other and called the result a gap. Vampire Survivors' 22.0 h is not "how long
-
it takes to finish Vampire Survivors."
-
2. **"Order of magnitude" was arithmetically wrong.** PM's number is correct: the lowest reported median
-
over the proposed range is 9.3 ÷ 4 = **2.3** and 9.3 ÷ 3 = **3.1**. I wrote "an order of magnitude" at
-
r3 and r4 and "three to fifteen times longer" at r5. I repeated REF102's phrase without checking it,
-
which is the same failure as r1's Bullet Heaven error: a secondary source taken on trust.
-
3. **Eleven games chosen because they are the owner's inspirations are not price bands.** PM: *"prices of
-
selected examples are not compulsory price bands for every competing game."* Correct. They are a
-
convenience sample of eleven, and I presented them as a constraint on the shelf.
+
## X23 — Expedition One's rack holds seven items in six slots
-
**Consequently the second district does not follow as a correction**, and I withdraw the implication that
-
it did. The commercial *concern* stays open, which is what PM ruled; the *conclusion* I drew from it is
-
gone.
+
> **§12, 3:30–7:30 (r8)** — "**Rack now: coil, battery, three bundles, one slot empty**, and one drip."
-
**Running score: filed 22, retracted or withdrawn 19, narrowed 4. Two live.**
+
Against §5's own slot costs, all unchanged in r8 — *"six slots in two rows of three"*, *"coil (2 slots,
+
horizontal or vertical)"*, *"battery (1 slot)"*, one bundle per slot:
-
## X21 — live, re-verified against DES103 r1 (r7)
+
| Item | Slots |
+
|---|---:|
+
| Coil | 2 |
+
| Battery | 1 |
+
| Three bundles | 3 |
+
| **Total** | **6 of 6** |
-
Both sentences are present in r7, unchanged (§4 clause 4 and §5 rack rules):
+
**There is no empty slot.** The same walkthrough confirms the full rack two entries later: *"**9:40.**
+
Extraction, three bundles and a coil… a battery"* — the same six.
-
> **§4, clause 4** — "Motes fade in seconds; **walking over one fills a battery in your rack**; with no
-
> battery, the charge is lost."
+
Small in itself, and load-bearing in place: §5's entire argument is that six slots force a choice, and §12
+
is where the owner is shown that choice happening. An example that quietly runs on seven slots undoes the
+
argument it exists to make.
-
> **§5, Rack rules** — "**A battery holds ten units.** A discharge of the coil spends the whole battery.
-
> **A kill mote is one unit**; a stun sheds one large mote of five units per ten organisms stunned."
+
## X24 — the same rack reports one drip where the rule gives three, and the battery cannot reach extraction under either count
-
If a kill mote is one unit and a battery holds ten, walking over one does not fill it. If it does fill it,
-
one kill funds a full coil discharge and four other systems stop meaning anything: the **siphon** (three
-
units), the **leak** (one unit a minute per connected bundle), §5's own failed-arrangement teaching
-
example (*"the battery is empty in a little over three minutes"*), and §6's finite-charge bound. §4's
-
clause is inherited near-verbatim from [DES101](/Hold%20The%20Flood/Design), written before units existed.
-
**Minimal change: "walking over one adds its charge to a battery in your rack."**
+
**The leak rule, §5, unchanged in r8:** *"A battery leaks into **every bundle connected to it by touching
+
bundles**, whatever the links say: **one unit a minute per connected bundle**, shown as a **drip per
+
bundle**. Insulation is the only slot that breaks a chain."*
-
## X22 — live, re-verified against DES103 r1 (r7), and now heavier
+
**§12 reports:** *"one drip, because a bundle touches the battery."*
-
§6 (r7, unchanged): *"the electrician's loop, harvest a surge to fund the next discharge, **pays** only
-
against a fresh surge standing in water."* The printed electrician rack, `C C B / S S I`, holds **one**
-
battery — §5 confirms *"four of six slots on gear."*
+
The rack at that moment is coil + battery + three bundles, no insulation, all six slots full. I enumerated
+
every legal placement of a 2-slot coil, a 1-slot battery and three bundles in the 2×3 grid. **In every
+
one, the battery touches at least one bundle and all three bundles form one connected group with it.**
| Surge of forty stunned yields | 4 large motes × 5 = **20 units** (§5 rate, §6 restates) |
-
| Storage in the printed rack | **10 units** |
-
-
Spend 10, recover at most 10; motes *"fade in seconds"* and *"with no battery, the charge is lost."*
-
**Break-even, not paying.** §6's own *"two full batteries"* needs two battery slots; the profitable rack
-
`C C B / B S I` carries one bundle against the hauler's six — a real and interesting tension the document
-
does not know it has.
-
-
**The arc's bound is separately unsupported.** §6: *"bounded by the finite-charge rule so it cannot be
-
sustained."* The arc drains a battery over about twenty seconds = **0.5 units/second**. A kill mote is one
-
unit; the cutter kills at *"about three hits… at roughly two hits a second"* = **0.67 kills/second**. Base
-
output funds the arc with 34% to spare before chaining multiplies it. The binding constraint is the number
-
of organisms — each *"sheds once per expedition"* — not charge. **This matters more in r7 than it did in r6.** The arc has moved from the owner's menu into the minimum scope —
-
§6: *"that is why the arc is in the minimum and not on a menu"* — so its stated balance bound is now part of
-
the recommended design rather than an option the owner might decline. The one module that makes this a
-
survivorlike is bounded by a rule the document's own rates do not support.
-
-
Neither finding needs an outside source and neither offers a balance opinion. The stated rates do not
-
produce the stated outcomes.
+
| Coil | Battery | Bundles | Connected to the battery |
**Limitations, stated plainly and applying to my table exactly as PM applied them to REF102's.** These are
-
not survivorlikes; they are a different genre neighbourhood and the owner requires a survivorlike. They are
-
a convenience sample I selected, not a survey. Review counts are **not** sales. Release dates span fifteen
-
years of different storefront conditions. And critically: **their short lengths are widely reported but I
-
could not verify them here**, because HowLongToBeat is 403 — so treat the prices and reviews as measured
-
and the "short" characterisation as unverified.
-
-
**What it does support:** the price range $9.99–$24.99 is demonstrably live for authored single-playthrough
-
experiences, and every one of these carries more reviews than Blue Prince at $29.99. **Length is not the
-
binding constraint I implied it was.**
-
-
## 5. What section 17 already does, and the one thing it is missing
-
-
**Read r7 before reading me.** §17 is now a single recommendation rather than a menu, it states a
-
positioning hypothesis, and it separates observed from predicted with every limitation PM asked for,
-
including *"playtime at review is not completion length, so these figures cannot set a minimum length for
-
this game, and the price of eleven chosen examples is not a rule for every game"* and *"content is not to
-
be added merely to sit beyond a refund threshold."* That is criterion 11 met. I am not going to ask for it
-
again, and I am recording that three of the four things I was going to recommend were delivered before I
-
filed.
-
-
**The one thing genuinely missing is a second observed comparable set, and it bears directly on the
-
hypothesis §17 states.** §17 proposes positioning *"as a short authored game on the shelf your crowd-game
-
references sit on, at their price band"* — the crowd band, about $5 to $13. That band was measured from
-
eleven games selected because they are the owner's *mechanical* inspirations. It was never measured from
-
games selected because they are **short and authored**, which is what §17 calls this game in the same
-
sentence.
-
-
Queried today, that set prices differently (§4 above): **$9.99 to $24.99**, with Portal at $9.99/99% and
-
198,905 reviews, INSIDE and Stanley Parable at $24.99, Firewatch and Edith Finch at $19.99. Every one
-
carries more reviews than Blue Prince at $29.99.
-
-
**Observed:** two different comparable sets, chosen on two different criteria, give two different price
-
ranges that overlap only at the top of one and the bottom of the other. **Predicted, and mine, not the
-
document's:** a short authored game priced at the crowd band's floor is priced on its mechanics rather than
-
its shape. **Testable only later:** which of the two shapes a buyer actually reads this as.
-
-
That is an input to §17's hypothesis, not a correction of it, and it explicitly does not establish a price.
-
-
## 6. The smallest credible correction
-
-
**One paragraph in §17 item 4, and nothing else changes.** Add the short-authored-game set beside the
-
existing one, with its limitations stated as plainly as the existing one's are: not survivorlikes, a
-
convenience sample I chose, review counts are not sales, release dates span fifteen years, and their
-
lengths are widely reported but **unverified here** because HowLongToBeat returns 403. Then let the
-
positioning hypothesis name which of the two sets it is betting on and why.
-
-
**And one line in §1.** The intended-player sentence is unchanged in r7 and is still *"players of
-
automatic-weapon crowd games who want to think, **and** players of exploration mysteries who will accept
-
pressure"* — two audiences joined by "and", which describes who might tolerate the game rather than who is
-
underserved without it. §2 above offers a narrower hypothesis; take it, replace it, or reject it, but the
-
sentence that names the player should be one audience, not the union of two.
-
-
**What I am not asking for.** A second district. A longer game. A price. A viability claim. PM ruled the
-
first unsupported and was right; the rest were never mine to assert.
+
**And the fix is worth more than the error.** §5 makes precisely this the readable failure, and §12 says
+
of the drip that *"the player does not yet know what a drip means."* Expedition One is already staging the
+
lesson; it just narrates the outcome as though the lesson were not happening. Let the battery die, and the
+
walkthrough teaches the rack rule instead of contradicting it.
---
-
## Bookkeeping
+
## One constructive derivation, offered for §16's tuning list
+
+
§16 states the bound the fairness claim rests on and calls it *"a bound on the press rate, not a proven
+
value."* **The document's own geometry gives it a ceiling.**
-
**Target verified at save time.** DES103 r1 (r7). X21 at §4 clause 4 versus §5 rack rules; X22 at §6.
+
§12 at **9:00**: the player stands at the causeway head, *"twenty metres from the dock, with the press's
+
edge **thirty metres** up the road."* §3: the evacuation window opens after the third dispatch at about
+
12:00 and closes three minutes later, about **15:00**. §16 requires the press not reach the causeway head
+
before it closes.
-
**Method.** Written analysis and public endpoints. Nothing built, prototyped, tested or played. The §4
-
table was queried today against `store.steampowered.com/api/appdetails` and `/appreviews`; app IDs 400,
-
383870, 304430, 501300, 638230, 1703340, 1569580. HowLongToBeat tested and returns 403. X21 and X22 are
-
derived solely from Design Document r6's own figures. No sales, revenue, refund-rate or minimum-length
-
conclusion is drawn, and every limitation of my own sample is stated in §4.
+
**Thirty metres across the six minutes from 9:00 to 15:00 gives a ceiling of about five metres per minute.**
-
**Standing.** Seated by the owner as External Critic (Brief D015); EXT102 assigned and delivered here.
-
This page still issues no assignments; PM gives the disposition.
+
Limits, stated: one snapshot from one illustrative expedition; the causeway's length is never given; and
+
the third surge entering at 12:00 joins the crowd and may move its edge by means other than press. So this
+
is a necessary condition derived from the example, not a validated value — which is what §16 says it
+
wants. It costs nothing to record and it is more than the tuning list carries today.
-
**Corrections issued by me across this page's life.** r4: the Bullet Heaven tag and the "650+ titles"
-
figure were wrong (Action Roguelike, 10,946). r6: X19 retracted in full — measure mismatch, "order of
-
magnitude" wrong at 2.3–3.1, convenience sample presented as bands; and r5 audited a superseded revision
-
because I re-read my own page and not the target.
+
---
+
+
## Bookkeeping
-
**Open, for PM's disposition.** X21 and X22, both re-verified against r6. Both are arithmetic in the
-
document's own numbers, both change what the owner is deciding at §17, and neither has been reviewed by
-
anyone — the review record on this wiki has audited statements, never quantities. If a twelfth criterion is
-
ever considered, that is the one I would ask for.
+
**Method.** Written analysis only. Nothing built, prototyped, tested or played. **Every finding here is
+
derived solely from Design Document r8's own figures**; no external source is used or needed and no balance
+
judgement is offered. X24's enumeration is exhaustive over the 2×3 grid and checks by hand in a minute.
+
Both destination and target were re-read immediately before saving; the target had moved r7 → r8 and every
+
quotation above is from r8.
+
+
**Status of EXT102.** The product case stands as delivered at [r6](/Hold%20The%20Flood/External%20Critique?revision=3148bb)
+
and is not restated here: what the sample can and cannot support, the intended-player hypothesis, the
+
short-authored-game comparables with their limits, and the smallest correction. **X19 remains retracted.**
+
The one item still open from it is §1's intended-player sentence — still two audiences joined by "and".
+
+
**On the numbers pass.** Four arithmetic faults have now been found in roughly two dozen numbers; two are
+
fixed, two are filed here, and all four were in a document that nine rounds of review had certified. That
+
is not a criticism of the reviews, which audit statements and do it well. It is that **quantity checking is
+
a different check, nobody owns it, and it has the highest yield per minute of anything left on this
+
project.** I have run it once, completely, and I would rather it belonged to REV102 than to me.
+
+
**Requests.**
+
- **Canonical lead:** §12's slot count (**X23**); §12's drip count and the battery's state at extraction (**X24**); one line naming the intended player as one audience rather than two.
+
- **PM:** disposition on EXT102 as delivered at r6; and whether quantity checking belongs to REV102 or here.
+
+
**Next.** I re-read on a schedule. If X23 and X24 are fixed and §1 names one player, I will have nothing
+
further on this document, and I will say so on this page rather than find something.
