Hold the Flood — Design Review

REV101 · r6 · 2026-09-06 14:25 UTC · Independent Design Critic · In review — re-review of Design r3 (a folded, glossaried body) and World and Mystery r5/r6 (a rule change I had not seen, plus fiction), with the outside reader's round-2 contradiction claims verified. r5–r1 are retained verbatim on the Archive sub-page and in page history (d3679b, 3fd6df, 698c13, 47d51d, 7ad187); every finding is indexed at the foot of this page.

What was re-reviewed

Artifact Revision Changelog (local, UTC+3) UTC Note
Design — DES101 r3 (new body; notes 1–3 folded; glossary) 0b4039 17:14:46 14:14:46 Read WLD r5 and Design Review r4; saved 3 s after REV101 r5, so did not see N11 or the frozen-body release — and reached both on its own
World and Mystery — WLD101 r5 (rule change) and r6 (fiction) 33dc2a → 430206 17:16:45 (r6) 14:16:45 r5 fixed N10, placed each beacon at its branch's far end, added "holds there", gave the extraction trace; r6 added definitions and in-fiction answers; diffed against r4 e54d6a
Clarity Questions — CLR101 r2 cba5eb 17:15:43 14:15:43 Round 2, Q22–Q25; treated as data, two claims verified below
Design Document; PM Reviews 404 at 14:22 UTC Tasks 254220, Brief a449b2, Team 3ddc81 unchanged; OWN101 still open

Verdict — unchanged: ready for owner concept steering (OWN101) — with one correction required before any owner-facing text is derived from these pages

The concept is intact and much clearer: Design r3 is the first revision an outsider could read end to end. But r5's rule change (surge path is now continuous) left three older sentences that state the opposite, and one of them is the sentence that prices A's central lever. That is N12 below. It does not affect A-versus-B; it must be fixed before the pricing paragraph or the signature scene is shown to the owner.

Status of carry-forwards after r3 / r5 / r6

Item Response (where) Status
N10 — "pulsing" in the path clause WLD r5 W1 path: "nearest energised beacon… re-evaluated continuously… with no energised beacon reachable, a surge spreads along the branch it entered"; item 3 gives the reason (a standing lure reads from the light convention and is counterable). Design r3 spine rule 3 carries the same wording Resolved — but see N12: the sentences written under the old reading were not revisited
N11 — do unpowered modules conduct? Design r3 §The rack: "every module except insulation" conducts; "a dark unlinked module still drains it"; leaking "ignores links". Reached independently of r5 Resolved — the lead chose the stricter rule; it makes a second module a real leak, which tightens the rack further
Extraction trace (no-panel first expedition) WLD r5 §"No-panel extraction trace": surge 3 holds at the causeway's interior end; player returns dock-ward through the culvert; the dock end is passable "by construction, not by timing" Resolved on paper — carry into DES102's written expedition; the open stretch is empirical, as stated
Finding 5 — readable-state table Still a DES102 commitment (Design r3 §Presentation) Open, correctly deferred
Pump-hall moment with hatch power-loss rule Still committed for DES102 Open, committed
Owner-readability (r5 checklist) Design r3: glossary (Q1–Q9), survivorlike defined (Q2), "loadout" for the player-facing meaning (Q3), run = expedition (Q4), combat and health (Q10, Q11), whole-game shape with an ending as owner decision 5 (Q12), motive and colony (Q13), title read literally and left provisional (Q14), notes folded (Q17), leak-versus-link (Q18); bookkeeping moved to the end (Q21, partly). WLD r6 supplies dispatch and forecast fiction (Q7, Q8) — a relay on its old timer, built to call crews to the powered branch, which the Flood answers — and Design r3 states the same fiction independently, pending confirmation Largely resolved. The r5 caveat ("not owner-readable") is lifted for Design r3's body. Residue: the decisions list still cites "W1 to W4 and S1 to S3" by code; Q21's appendix is a DES102 task
Finding 2 — cost of diversion See N12: the four-cost paragraph (WLD §"Cost of diversion") and Design's pricing sentence were written under the per-dispatch reading that r5 replaced Conditionally re-opened until the cost of a mid-surge re-route is stated

New findings — priority order

N12 — The panel now moves entered surges; three sentences still say it cannot (CLR101 Q22, verified)

  • Where: World and Mystery 430206 — W1 path ("after entry, a surge moves toward the nearest energised beacon it can reach, re-evaluated continuously") and §Topology ("re-routing the panel after entry is what drags a surge across the district toward the new light") versus W2 ("Re-routing at the panel affects only surges not yet dispatched") and §"Cost of diversion" cost (3) ("committed surges do not turn back, so a diversion made after dispatch buys nothing this surge"). Design 0b4039 — spine rule 3 (continuous path) versus the pricing sentence ("a surge already dispatched does not turn back").
  • Why it fails: under continuous path, switching the panel darkens one fixed beacon and lights the other, so every surge in the district walks toward the new light. W2's sentence has no intake/path qualifier and has not been reworded since W1 was split in r4; cost (3) is simply false under r5; "does not turn back" is true of intake and false of path. The reader's framing is correct: the per-dispatch reading makes the panel a planning tool used between surges; the continuous reading makes it a lever that drags a surge off you mid-emergency. Both designers state the second (WLD item 3, Design spine 3); the unrevised sentences state the first.
  • Consequence: the cost-of-diversion argument — the closure of Finding 2 — was made for the first game. For the second, the mid-surge re-route is unpriced in text: the four costs (panel in the open; lighting a branch opens its hatch and invites the next surge; committed surges; the held dock) still apply, and the world designer's counterplay reasoning is sound, but nothing states what a "panic switch" costs when a surge is already on you. That is A's central lever and the paragraph the owner will read.
  • Category: contradiction (same page and cross-page); load-bearing.
  • Minimal change: (1) reword W2 to the split: "Re-routing never changes an entered surge's intake and never teleports it; it does change every entered surge's path, because it changes which beacon is lit." (2) Replace cost (3) with the cost of a mid-surge switch — e.g. that the dragged surge crosses the district through the low end, so the route it takes to the new light is the route it now occupies, and the hatch on the darkened branch shuts. (3) Change Design's "does not turn back" to "keeps its intake". Then re-read the four costs once under the continuous reading and say whether Finding 2 still closes; I expect it does, but it has to be argued, not inherited.

N13 — The electrician's scene needs the surge in water; r5's topology has it holding beside a dry beacon (CLR101 Q23, verified; half already fixed)

  • Where: Design 0b4039 §Signature interaction ("wait on the ledge for surge two to wade into the channel before triggering") and §Loadouts Electrician ("waits for the surge to wade into the yard channel") versus WLD 430206 §Topology and Design 0b4039 §Topology ("the yard beacon stands at the pump hall… A surge enters beside its beacon and holds there while it stays lit") and WLD r6's definition ("Intake: … the pump hall").
  • Why unclear: the scene needs surge two standing in the shallow channel; the rule has it entering at the pump hall and holding beside the beacon. No sentence places the yard intake or the beacon's holding ground in the channel. (The scene's other half — "surge one is dispersing" versus "holds" — Design r3 already corrected to "holding at the causeway's far end".)
  • Consequence: the one concrete moment meant to sell A does not follow from the rules as written. Small to fix, large if left, because it is also the electrician's whole loadout.
  • Category: missing design detail.
  • Minimal change: one sentence in both topologies: "The yard intake opens into the shallow channel in front of the pump hall; a surge holding at the yard beacon stands in that water." That also makes the yard branch inherently the wet one, which is what the coil, the flooded dock and the conducting rack all want.

N14 — The pump's upkeep exists in fiction and not in rules

  • Where: Design 0b4039 §Fantasy and motive ("The pump burns salvage; that is why you haul. Stop hauling and the dock floods") versus §Gathering and colony (bundles are banked or spent on a channel pump; pump capacity is one exclusive choice; two additive repairs — no upkeep rule) and §Persistence (colony state persists; nothing decays).
  • Why unclear: either there is an upkeep cost per expedition, or there is not. If there is, the colony becomes a treadmill in which an investigative expedition that returns light is punished — the meta-level form of "pressure that leaves no room for curiosity", and a gathering grind by another name. If there is not, the motive paragraph promises a stake the rules never collect.
  • Consequence: decides whether exploration is the reward channel (Design r3's own argument against kill XP) or competes with a maintenance bill.
  • Category: missing design detail; owner-requirement risk if upkeep is chosen (Brief: colony "without becoming a disconnected chore").
  • Minimal change: one sentence. Recommended: no upkeep — the pump is fuelled by banked salvage once, and the flood threat is what makes the held-dock choice exclusive; "stop hauling and the dock floods" then reads as the colony's long-run stake, not a per-expedition tax. If upkeep is wanted, state the rate and say what a zero-salvage expedition costs.

N15 — Minor: "Quiet 3, shorter" is the same length (CLR101 Q24)

Design 0b4039 §Rhythm: Quiet 2 is minutes 5–8, Quiet 3 is minutes 10–13; both three minutes. Either tighten the numbers or drop the word. Wording.

N16 — Scope of the minimum: three mystery tiers, one designed

Design 0b4039 §The whole game proposes three tiers (false refuge; the interior; the relay's source) and an ending at the source in 12–20 expeditions. Only tier one is designed. Not a defect at concept stage — it is presented as owner decision 5 — but Tasks criterion 9 (minimum complete intended experience) will require DES102 to state which tiers are in the minimum and sketch tiers two and three in a paragraph each as recombinations of the spine rule, not as new machine families or a lore catalogue. Scope; carry-forward.

What works in r3 / r5 / r6, and why

  • Design r3 can be read by someone who has not read the wiki. A one-line glossary, plain motive, combat and health stated, the whole game shaped, bookkeeping at the end. This is the Tasks criterion 1 standard, reached without the owner-facing document yet existing.
  • The two designers converged on the same dispatch fiction independently (a relay on its old timer, built to call crews, that the Flood answers). A fiction that two authors reach from the rules is a fiction the rules support.
  • N10 was closed with a reason, not a word (WLD item 3): continuous was chosen because a standing lure is readable and counterable. N12 is the cost of that reason; it is the right kind of cost.
  • The extraction trace holds by construction. "Withdrawal never requires solving this" is now shown, not asserted.
  • The lead adopted the stricter rack rule (dark modules drain) without being asked, which makes the rack's one decision sharper.
  • The outside reader's method is worth keeping: for every sentence carried into DES102, ask whether it was written before or after the intake/path split. Adopted into the DES102 checklist below.

Recorded for later empirical validation — not defects

  • Whether a panel that can drag an entered surge dominates (depends on N12's re-pricing).
  • The open stretch between culvert exit and dock (WLD r5).
  • Everything under r2–r5.

DES102 checklist (current)

Tasks criteria 1–10; N12–N16 closed; Finding 5 table with owner-approval residue; pump-hall moment with hatch power-loss rule; the extraction trace in the written expedition; tiers two and three sketched as recombinations; codes to an appendix; and the reader's pass — every carried sentence checked against the intake/path split.

PM report — r6

  • Task: REV101. Artifact: Design Review r6, In review; r5–r1 retained.
  • Reviewed: Design 0b4039; World and Mystery 430206 (r5 33dc2a via diff); Clarity Questions cba5eb. Design Document and PM Reviews still 404. Tasks/Brief unchanged.
  • Changed decisions: none by this role. Verdict unchanged; Finding 2 conditionally re-opened pending N12.
  • Evidence: written comparison; diff of WLD r4→r6; the reader's Q22 and Q23 checked against the exact sentences and confirmed (Q23 half already fixed in Design r3). No players, sessions, scores or asset checks; nothing built, prototyped, tested or created.
  • Remaining risk: N12 is the only item that must precede owner-facing text; N13/N14 are one sentence each; N15/N16 are DES102. PM pages remain stale (Tasks still shows DES101/WLD101 "Ready", REV101 "Waiting for first submission"); CLR101's author is not on the recorded Team — PM to decide whether to adopt the page; two lead sessions still unnamed.
  • Next handoff: lead and world designer — N12 (three sentences and a re-argued cost paragraph), N13 (one sentence, both topologies), N14 (one sentence). PM — record the working direction under OWN101; decide CLR101's status. I review DES102 when it exists and will not revise again for DES101/WLD101 unless a change is material. One exact PM request: record the working direction (A, B, or premise change) and confirm whether the spine rule, W1–W4 and S1–S3 are carried into DES102 as candidate rules.

Where the earlier reviews are, and where every finding lives

Added by the wiki editor, 2026-09-06. REV101 r5–r1 used to sit below this line, 62 KB of them. They are now on Design Review / Archive, verbatim and unedited, and each is separately in page history. Nothing was summarised or dropped. This index exists so that a citation of any finding, from any page, still resolves in one click.

Reviews: r5 · r4 · r3 · r2 · r1

Finding Raised in Read it at Status per r6
Finding 1 — integration removes the reason A was recommended r1 archive Resolved at r2
Finding 2 — free unlimited diversion vs A's only escalating pressure r1 archive Resolved at r2; conditionally re-opened by N12
Finding 3 — the 2×3 rack cannot produce a placement decision r1 archive Resolved at r2
Finding 4 — in-run progression denied for kills, unspecified otherwise r1 archive Resolved at r2
Finding 5 — readability demands concentrate where free assets are least likely to fit r1 archive Carried to DES102
Secondary 1–5 (Secondary 3 withdrawn) r1 archive Closed or carried at r2/r3
N1 — two pulsing beacons, no priority rule r2 archive Resolved
N2 — what sheds charge, stunned only or killed too r2 archive Resolved
N3 — topology lists one dock, the colony rule needs two r2 archive Resolved
N4 — the Off intake has no place r2 archive Resolved
N5 — "coil optional" alongside a coil-dependent spine r2 archive Closed
N6 — two build vocabularies r2 archive Closed (now "loadout")
N7, N8, N9 — battery links; sign wording; stale cross-reference r3 archive Resolved
N10 — "pulsing" in the W1 path clause r4 archive Resolved at WLD r5
N11 — links versus leaks (CLR101 Q18) r5 archive Verified, not a contradiction
N12–N16 r6 above, on this page Open

Vocabulary used in these findings is defined on the Glossary.