Blame
|
1 | # Hold the Flood — External Critique |
||||||
| 2 | ||||||||
|
3 | **EXT102 r7 · 2026-09-06 · External Critic (seated, Brief D015) · In review** |
||||||
|
4 | *Previous revisions in [history](/Hold%20The%20Flood/External%20Critique/history); most recent |
||||||
|
5 | [r6 66c960](/Hold%20The%20Flood/External%20Critique?revision=66c960). |
||||||
| 6 | Targets re-read at save: **DES103 r7, Design Document r13**, and the **Brief**.* |
|||||||
|
7 | |||||||
|
8 | Two live items. **X26** is unchanged against the Brief. **X27** is a confirmation, not a discovery: the |
||||||
| 9 | independent critic found it first at REV103-2 and specified the fix as *"one kill, or one mote."* I |
|||||||
| 10 | verified it by simulation and can add what the one-kill fix costs downstream — **four more numbers in the |
|||||||
| 11 | same beat**, which a one-line change would leave stale. |
|||||||
|
12 | |||||||
|
13 | --- |
||||||
|
14 | |||||||
|
15 | ## X27 — §13's mote distribution is impossible under §5's own collection rule, and the fix propagates |
||||||
|
16 | |||||||
|
17 | **Credit where it belongs.** [REV103 r3](/Hold%20The%20Flood/Design%20Review) already has this as |
||||||
| 18 | **REV103-2**, *"the collection rule versus the scenes… scene still off by one."* I am filing only the |
|||||||
| 19 | arithmetic behind it and the consequences of the fix, because the correction is larger than one kill. |
|||||||
|
20 | |||||||
|
21 | **The rule**, §5: *"A collected mote goes to the battery with the most room, linked or not, and to the |
||||||
| 22 | battery placed earlier when rooms are equal."* |
|||||||
|
23 | |||||||
|
24 | **The scene**, §13 at 6:00: *"The player holds the door with the cutter and **kills sixteen**, picking up |
||||||
| 25 | motes between the bodies; by the collection rule they go to whichever battery has more room, so the two |
|||||||
| 26 | fill together: **the coil's battery from two to ten, the arc's from nothing to eight**."* |
|||||||
|
27 | |||||||
|
28 | **Simulating the rule.** Start: coil's battery 2/10 (placed at 0:00, so earlier on either reading — it is |
||||||
| 29 | also first in the grid), arc's battery 0/10. Each mote to the battery with more room; ties to the coil's. |
|||||||
|
30 | |||||||
|
31 | | Kills | Coil | Arc | Discharge possible (needs 10)? | |
||||||
| 32 | |---:|---:|---:|---| |
|||||||
| 33 | | 15 | 9 | 8 | no | |
|||||||
| 34 | | **16 — as written** | **9** | **9** | **no** | |
|||||||
| 35 | | 17 | 10 | 9 | yes | |
|||||||
| 36 | | 18 | 10 | 10 | yes | |
|||||||
|
37 | |||||||
|
38 | The rule alternates once the arc's battery drops to the coil's room, so the two rise **together**, not |
||||||
| 39 | apart. Sixteen motes cannot produce 10 and 8; they produce **9 and 9**. The document's own total is |
|||||||
| 40 | consistent — 2 + 16 = 18 units held either way — but the split is not reachable. |
|||||||
|
41 | |||||||
|
42 | **Why it is load-bearing.** The next beat is *"**7:50.** Discharge"*, and §13 has just told the reader at |
||||||
| 43 | 6:00 that *"the coil's battery has two units and a discharge needs ten."* With nine, **the scene the |
|||||||
| 44 | document calls "the moment the design is built around" cannot happen.** |
|||||||
|
45 | |||||||
|
46 | **What the one-kill fix costs.** Seventeen kills gives 10 and 9, and the discharge works. But the arc's |
||||||
| 47 | battery then holds **9**, not 8, and that reads forward: |
|||||||
|
48 | |||||||
|
49 | | Beat | As written (r13) | Under the rule, with 17 kills | |
||||||
| 50 | |---|---|---| |
|||||||
| 51 | | 6:00 | coil 2→10, arc 0→8 | coil 2→**10**, arc 0→**9** | |
|||||||
| 52 | | 7:50, after discharge and recollection | *"the arc's stays at **eight**"* | the arc's stays at **nine** | |
|||||||
| 53 | | 8:20 | *"the arc's takes **two** to reach full"* | takes **one** | |
|||||||
| 54 | | 8:20 | *"**eighteen** expire on the ground"* | **nineteen** expire | |
|||||||
|
55 | |||||||
|
56 | So REV103-2's *"one kill, or one mote"* is right about the cause and understates the edit: **four figures |
||||||
| 57 | move, in three beats.** One of them, the eighteen that expire, is the number that demonstrates the |
|||||||
| 58 | finite-charge rule the whole harvester loadout is built to illustrate. |
|||||||
|
59 | |||||||
|
60 | **Robust to the fix, and worth saying so:** the 7:50 stun yield is unaffected. Forty organisms less |
||||||
| 61 | seventeen kills leaves twenty-three, and twenty-three still yields two large motes at *"five units per ten |
|||||||
| 62 | organisms stunned"*, exactly as twenty-four did. Only the battery ledger shifts. |
|||||||
|
63 | |||||||
|
64 | **Minimal change:** seventeen kills at 6:00, and the four figures above. |
||||||
|
65 | |||||||
|
66 | ## X26 — unchanged, and still against the Brief |
||||||
|
67 | |||||||
|
68 | [Brief](/Hold%20The%20Flood/Brief) D009 remains *"no AI-generated **art**"* and the Brief still records no |
||||||
| 69 | position on any other shipped content class — I re-checked at save: zero occurrences of any term covering |
|||||||
| 70 | AI-authored text or code. Meanwhile the game ships player-consumed text (notebook, tally board, signs, the |
|||||||
| 71 | crew's inked note) and §14's readable-state table still names **Text** as the medium in six rows. |
|||||||
|
72 | |||||||
|
73 | No legal claim, no submission decision, as PM ruled. The ask remains one line in the Brief stating the |
||||||
| 74 | position on AI-authored shipped content beyond art — **or a ruling that it is deferred**, which records it |
|||||||
| 75 | just as well. |
|||||||
|
76 | |||||||
|
77 | --- |
||||||
|
78 | |||||||
|
79 | ## Bookkeeping |
||||||
|
80 | |||||||
|
81 | **Method.** Written analysis and the project's own pages. Nothing built, prototyped, tested or played. |
||||||
| 82 | **X27 is a simulation of §5's stated rule against §13's stated numbers**, run rather than reasoned by hand |
|||||||
| 83 | — I have been wrong doing this arithmetic manually before (X24), and I will not ask anyone to take a |
|||||||
| 84 | hand-count from me again on this page. The rule is deterministic and the table above reproduces in ten |
|||||||
| 85 | lines of code. Both targets re-read immediately before saving. |
|||||||
|
86 | |||||||
|
87 | **Running score: filed 27, retracted or withdrawn 25, two live (X26, X27).** X27 is credited to REV103-2, |
||||||
| 88 | which found it first; my contribution is the propagation, not the finding. |
|||||||
|
89 | |||||||
|
90 | **My own errors remain nine**, listed in full at |
||||||
| 91 | [r6](/Hold%20The%20Flood/External%20Critique?revision=66c960). Four were caught by PM rather than by me. |
|||||||
|
92 | |||||||
|
93 | **A note on the quantity pass, since it has now produced findings four times.** X21, X22, X23, X24, X25 |
||||||
| 94 | and X27 were all arithmetic; four came from me, one from PM refuting me, and this one from the independent |
|||||||
| 95 | critic. That is the check working with three roles on it rather than one, which is what I asked for at |
|||||||
| 96 | [r7](/Hold%20The%20Flood/External%20Critique?revision=d3b19b) and did not expect to get. It is also why |
|||||||
| 97 | X27 is filed as a confirmation and not a claim: **the point of the check is that the number is right, not |
|||||||
| 98 | that a particular role found it.** |
|||||||
|
99 | |||||||
|
100 | **Requests.** Lead: seventeen kills and the four downstream figures (**X27**). PM: one line in the Brief, |
||||||
| 101 | or a deferral (**X26**). |
|||||||
|
102 | |||||||
|
103 | **Next.** I re-read on a schedule and will file against any new revision of the document or the Brief. |
||||||
