2026-09-06 21:50:48
Anonymous:
REV104 r2: review of Campaign DES104 r1 (9d3590) and PMR004 D022-D024 against criteria 1-11; contract 69024c checked vs DD r14/r15 and World r20; REV104-1..-5 verified at World r21 9aab5e; per-beat ledgers on 3.1-3.3; REV104-6..-10 opened; r1 moved to Archive/REV104 verbatim
hold the flood/design review.md ..
@@ 1,86 1,169 @@
# Hold the Flood — Design Review
-
**REV104 · r1 · 2026-09-06 16:52 UTC · Independent Design Critic · In review** — first critique under PMU004, of the first substantive DES104 section to arrive: **WLD103 r19–r20, the campaign mystery thread**, on World and Mystery r20. Tasks says REV104 may "critique available substantive sections as they arrive; no claimed future acceptance"; this does that and nothing more. **REV103 is closed below**: its four integration items are resolved on their owning pages, with one mirror pending. REV103 r5–r1 are on the [REV103 archive](/Hold%20The%20Flood/Design%20Review/Archive/REV103); REV102 r6–r1 on the [REV102 archive](/Hold%20The%20Flood/Design%20Review/Archive/REV102); REV101 r8–r1 on the [REV101 archive](/Hold%20The%20Flood/Design%20Review/Archive); every revision is in [page history](/Hold%20The%20Flood/Design%20Review/history) (REV103 r5 205bfb · r4 711ef4 · … · REV101 r1 7ad187).
+
**REV104 · r2 · 2026-09-06 18:55 UTC · Independent Design Critic · In review** — review of **DES104 r1, the Campaign page at 9d3590**, and PMR004's decisions D022–D024, against criteria 1–11 and the REV104 criteria pre-registered at REV103 r5: the shared-rule contract first, then per district the Expansion Brief's six, with per-beat ledgers on every written expedition and a shared-rule diff per district. The contract r2 (69024c) is checked against the Design Document r14/r15 and World r20 as the lead asked; REV104-1 to -5 are verified at the revisions that answer them (World r21 9aab5e; contract 69024c); the four staffed designers' pages are read for conflicts with the contract, not re-reviewed after PMR004 and PMR005. REV104 r1 is on the new [REV104 archive](/Hold%20The%20Flood/Design%20Review/Archive/REV104); REV103 r5–r1 on the [REV103 archive](/Hold%20The%20Flood/Design%20Review/Archive/REV103); REV102 r6–r1 on the [REV102 archive](/Hold%20The%20Flood/Design%20Review/Archive/REV102); REV101 r8–r1 on the [REV101 archive](/Hold%20The%20Flood/Design%20Review/Archive); every revision is in [page history](/Hold%20The%20Flood/Design%20Review/history) (REV104 r1 80a882 · REV103 r5 205bfb · r4 711ef4 · … · REV101 r1 7ad187).
## What was reviewed
| Artifact | Revision | UTC | Note |
| --- | --- | --- | --- |
-
| Brief D019–D021; Tasks; Team; Hub; PM Reviews — **PMU004 rollout** | 1bd68a; eb8c03; d00fad; 4ef1f3; 94e459 | 16:38–16:41 | Owner: larger campaign, many districts (D019). DES104, WLD103, EDT102 Ready; four designers proposed, unstaffed; **REV104** Blocked on DES104 with the section-by-section clause; "no micro-ledger review loop should block parallel campaign drafting" |
-
| **World and Mystery — WLD102 r18, WLD103 r19, r20** | d1d56a → 7699de | 16:37–16:41 | r18 closes REV103-9; r19 is the first WLD103 deliverable; r20 adds the evolving-hypotheses table |
-
| **Design Document — DES103 r8 (document r14)** | ec1b6c | 16:32 | Against REV103 r4 and World r17: §13 re-tallied under the collection rule; the weir clause lifted; the last stale sentence removed |
-
| Team / Expansion Prompts; Cutter; Equipment; Enemies; Colony | all 200 | | Created during PM's rollout, minutes after REV103 r5 checked them |
+
| **Campaign — DES104 r1** | 9d3590 (34dc09 plus CAM101's adoption note) | 17:11 | Read in full. §3's three written expeditions re-tallied beat by beat under the contract's rules; each district's shared-rule diff checked against clauses 1–6 |
+
| PM Reviews — PMR004 | e8c3d4 and its sub-page | 17:54 | D022–D024; §1–§4; this role's assignment: "Review actual 9d3590/current identified successor and PMR004 decisions against criteria 1–11; verify corrections only at actual revisions" |
+
| PMR005 | d15967 | 18:33 | Combat reconciliation; "additional evidence, not an independent acceptance". Read; nothing in it re-reviewed |
+
| **Mechanics / Power and Attraction r2** | 69024c | 16:58 | Checked clause by clause against Design Document r14 ec1b6c §1, §3–§5 (r15 5f9fbb leaves those sections unchanged) and World r20's "What stays fixed everywhere" |
+
| **World and Mystery r21** | 9aab5e | 18:31 | D024 developed; diffed against r20 7699de. REV104-1, -3, -4, -5 verified here |
+
| Design Document r15 | 5f9fbb | 16:58 | §11's mirror of World r18 verified (REV103-9 closed on both pages); scope note |
+
| Districts r3; The Collector r3; The Head-works r3; Pumping District | 699c8e; 29ece6; 999d84; 63d451 | 18:30–18:35 | CAM101 after PMR004. Read for shared-rule diffs and for conflicts with the Campaign page |
| Equipment; Inventory and Charge | a44990; 73eb77 | 17:12–17:13 | EQP101. E1 (eight cells) and E3 (selected priority) read as the rules D023 adopts |
+
| Colony | a1046d | 17:03 | COL101. Read against the no-upkeep baseline |
+
| Brief; Tasks; Expansion Brief; Team | 70b6b1; 469c70; 8e517e; 26bb6f | 17:40–18:36 | Canonical. D022–D024 recorded; REV104 Ready; four designers staffed by submission |
-
## REV103 — closed
+
## Verdict — **revise: one ledger, one integration pass, two tables of missing detail, two sentences**
-
All four integration items are resolved on their owning pages; each correction was read, not inferred.
+
The Campaign page does what the pre-registered criteria asked, in the order they asked it: the contract is stated first, and the three deep districts are written as diffs against it, each with two loadouts that differ in what they do, an enemy combination with a precedence question a single role cannot pose, a six-part discovery chain with its redundant form named in another district, consequences stated as rules, an asset table that claims nothing, and a charge ledger. Two of the three ledgers close to the unit under the rules as written, and the tram crew's alternation (5 / 0 → 8 / 7) applies the collection rule that REV103-2 spent four revisions on, correctly. §8 refuses an hours figure and says what would earn one. That is the standard this role asked for, met on paper by two districts.
-
| Item | Correction, quoted | Verified |
-
| --- | --- | --- |
-
| **REV103-2** (residual) — one unit at the discharge threshold | r14 §13: "Both batteries are empty, so by the collection rule the first mote goes to the earlier-placed battery, the coil's, and the second to the other… one in each"; "kills seventeen… the coil's battery from one to ten, the arc's from one to nine"; 7:50 "the arc's stays at nine"; 8:22 "the coil's battery takes ten and the arc's takes one to reach full; nineteen expire". Ledger: 1 / 1 → 10 / 9 → 10 / 9 → 10 / 10, expired 19 | **Resolved.** Re-tallied from the rule: identical to the numbers REV103 r3 derived |
-
| **REV103-7** (residual) — the weir clause | r14 §11 mirrors r17's two supplies with the weir ("weir" ×4) | **Resolved** |
-
| **REV103-8** (residual) — stale PM-report sentence | r14: the sentence is gone; Appendix B "no superseded live wording remains, this paragraph included" | **Resolved** |
-
| **REV103-9** — the relay's channel | World r18, "Two waters, stated once": "The relay's race is the sluice-head channel *above* the weir: flowing water, never energised… V3 joins the head pool to the channel *below* the weir, never to the race, so the valves cannot light the yard from the relay's side… Drain R empties the race: the wheel stops, the drum stops… the panel's power positions, the beacons, the hatches and GJ… keep working. This states one readable exception to clause 2, that the relay is a source and not a consumer." | **Resolved on the world page, geometrically** — the hydraulic reading REV103 r4 recommended, made true by where the weir is. **One mirror pending:** r14 §11's Understand row still reads "the relay is a device under the power clause, working only while its channel carries current"; §11 should lift r18's row and paragraph |
+
What fails: the Tidal Barrier's ledger collects a harvest that fades a minute away from the surveyor, and with it the district's stated lesson (REV104-6); PMR004's D023 has since replaced the rack size and the collection rule that every loadout, both closing ledgers and §4's charge argument are computed on, and neither the Campaign page nor the contract yet reflects it (REV104-7); the first battery in each written expedition is filled by a beat the pursuit and collection rules do not support (REV104-8); the two new panels never say which position selects which intake or which beacon flashes, which is the one thing the contract says a panel does (REV104-9); and two sentences contradict the precedence (REV104-10). None is a rule change; all are within the lead's own method. REV104-1 to -5 are answered at World r21 and contract 69024c, with the contract's mirrors pending. Whole-campaign acceptance is not offered and was not asked for; r1's section critique stands as a contribution, as PMR004 records it.
+
+
## REV104 r1 items, verified at the revisions that answer them
+
+
| Item | Where answered | Quoted | Status |
+
| --- | --- | --- | --- |
+
| **REV104-1** — what a local dispatch requires | World r21 9aab5e, "W1, extended for the campaign" (D024) | "a district's beacon flashes, and its intake is chosen, when its local drum turns **and** the trunk permits that district: the drum supplies the timing, the trunk supplies the permission, and either alone makes nothing" | **Resolved on the world page.** Contract clause 3 still carries the placeholder ("this contract will carry the sentence the world designer adopts"): mirror pending, lead |
+
| **REV104-2** — the Collector's meters against clause 4 | Contract 69024c clause 4 | "charge never leaves a district with the player; what a district's own machines meter or move is that district's design" | **Resolved**; not reopened. Collector r3 §4 builds on it correctly: "Charge is earned here and spent here. Nothing carries it out" |
+
| **REV104-3** — the empty flash | World r21, "The empty dispatch" | "the beacon flashes, the thin cable pulses, and nothing arrives… within the arrival window the forecast's intake marker hollows out, and the notebook records 'an empty dispatch'" | **Resolved on the world page.** Collector r3 §3 states the same W1 clause as its one requested contract change; the two pages agree. Contract mirror pending |
+
| **REV104-4** — what powers the district's circuit | World r21, the six-state table, under D024; Head-works r3 §2 | "Fixed power — source: the cell bank at the Head-works, filled by the Collector's wheels; connection: the thick power trunk to the district's own circuit"; the Head-works names the dry break ("every powered line in this district stops at the gallery") and the feed | **Resolved provisionally** (PM's D024; not owner-approved). Contract clause 2's "not stated on any page" is now stale: mirror pending |
+
| **REV104-5** — the routing bank priced by rule; "dark" means the Shut regime | World r21, "The routing bank's price"; Campaign §3.4 | "costs the forecast in the districts it leaves unpermitted (Campaign §3.4), and a district left dark long enough falls to the Shut regime on the next visit; it is a lever with a standing cost, not a free plan" | **Resolved as a rule.** Balance empirical, as the page says |
+
| r1 minor — the head-works' clue in one district only | Head-works r3 §6 | proposes the Lock Flight's greased levers as the second form, "for the World designer to accept or replace" | Open until the world page adopts a second form; the essential-clue table at r21 still has both forms of "the network is maintained" in the Head-works |
+
| REV103-9 — §11 mirror | Design Document r15 5f9fbb §11 | mirrors World r18's two-waters paragraph and the weir clause | **Closed on both pages** |
+
+
One consequence of r21 to record for the contract: "Flowing water conducts like any water… The race is unenergised because it is an unfed body." Clause 2's "the race above the weir, which carries no charge" stays true; the reason should read *unfed*, not *flowing*, as Head-works r3 §2 already has it.
+
+
## The contract r2 against the Design Document and the world page — the lead's request
+
+
Checked clause by clause against Design Document r14 ec1b6c §1, §3, §4 and §5 (r15 leaves them unchanged) and World r20's "What stays fixed everywhere, and what a district may add". **It agrees with both, clause for clause**, and §9's list of what the seed lacked is filled as stated. Four things to carry or correct, none a rule change:
+
+
1. **The leak rate is missing.** Clause 1 says a bundle touching a battery leaks, "shown as one drip per bundle"; the Design Document's "one unit a minute per connected bundle" is the number every ledger's expired column depends on (expedition one loses four units to it). Inventory 73eb77's baseline table carries it; the contract should.
+
2. **How a mote is collected is missing.** Clause 4 says where a collected mote goes; the Design Document says how: "walking over one adds its charge". REV104-8 turns on it, and D023's "pickup" (Inventory E3, E5) is the same mechanic under a new priority rule. One clause.
+
3. **What conducts when dry.** Clause 1 gives water and wet bundles; clause 2 "the water or line it stands on". Campaign §3.2's rail diff says "a channel need not be water, and the contract says so from here on" — it does not yet; and §3.1 says crane parts "are dry metal and do not conduct" while the rail is "a metal channel… a dry conductor". One sentence settles both: lines (cables, rails) conduct; a dry bed, loose cargo and equipment housings do not.
+
4. **Two pointers and two mirrors.** Clause 1: locks are in Campaign §3.1, not "section 7 of the Campaign page". Clauses 2 and 3: REV104-4 and REV104-1/-3 are answered at World r21 and should be carried, as clause 3 promised.
+
+
Noted, not raised: clause 8's "enemy variants by size and tint" against Campaign §4's "not by tint alone" — PMR005 6 disposes of it as a clarification, and this role agrees the two sentences can both be true.
+
+
## The three written expeditions, re-tallied
+
+
Method as pre-registered: for every beat, slots and contents; links and leaks by adjacency; battery units; which beacons are lit and by what; each crowd's nearest reachable lit beacon; door states; the clock.
-
**Three pointers in REV103 r5 retracted.** The Expansion Prompts page, and the Cutter, Equipment, Enemies and Colony pages, all exist; PM created them within minutes of that check, mid-rollout — the same error the editor made and withdrew, and the same lesson ("do not flag a gap in the middle of somebody's rollout"). Hub and Tasks now carry the expanded scope. Nothing remains of those three lines.
+
**3.1 The Lock Flight, lockkeeper (six slots).** `C C B / S S I`, link B→C: the battery touches the coil and the insulation; the bundles touch the coil's housing, each other and the insulation — no leak, as stated. 3:30, ten kills → 10 / 10 stored. 5:00, the discharge needs a full linked battery ✓, spends ten; the head basin is energised for seconds and the door, a device on the Head's line, opens ✓; nothing in the water, nothing sheds ✓. 5:30, rack full, one bundle dropped for one part: `C C B / S P I`, six of six ✓. 7:20, the flow rule: floaters yield to flow while it flows ✓; the Middle joins the Tail while L1 is open and the Tail is on the quay circuit, so the Middle is energised for the flush — the surveyor is on the lever, not in the water ✓. 8:10, extracted six slots ✓. **Closes to the unit: dropped 10, collected 10, spent 10, expired 0.** One beat fails pursuit (REV104-8); two sentences fail the precedence (REV104-9, REV104-10).
-
## REV104 r1 — the campaign mystery thread (WLD103 r19–r20), against the pre-registered criteria
+
**3.2 The Tram Incline, tram crew (nine slots).** `C C B / A B I / S K S`, links top B→C, middle B→A: the top battery touches the coil and the insulation; the middle battery touches the arc, the coil, the insulation and the kit; no bundle touches either — no leak ✓; both links by adjacency ✓. 3:30, the heavy's large mote, five units → 5 / 0 (the tie by placement, asserted) ✓. 4:30, ten kills under most-room: 5 / 0 → 5 / 5 → 6 / 5 → 6 / 6 → 7 / 6 → 7 / 7 → 8 / 7 ✓; the page's own working is right. 5:30, lamp off, lever down: no lit beacon is reachable (the yard beacon is on the Gates circuit, dark under Rail; the summit has none) → spread ✓; the tram descends because the rail is still powered ✓. 6:00, two bundles → 9 / 9 ✓; they touch the arc's housing, the kit and the insulation — no leak ✓. 8:00, eighty enter a dark yard → spread ✓. 9:40, fifteen lost at the dock ✓. **Closes: dropped 15, collected 15, expired 15 at the dock.** What fails: the collection at 4:30 (REV104-8) and what the panel selects (REV104-9). Under D023 the ledger is superseded (REV104-7).
-
**Verdict on this section: it meets the mystery criteria in structure and is the right template for the campaign; five sentences are needed before Campaign builds districts on it, one of them load-bearing.** This is a critique of a contribution, not of DES104, which does not yet exist.
+
**3.3 The Tidal Barrier, tidewatcher (nine slots).** `C C B / S I K / S S –`, link B→C: the battery touches the coil and the kit; no bundle touches it ✓. The header says "one empty slot, two empty bundle slots"; the drawing, the loadout text ("three bundles, and one empty slot") and the ledger ("four empty"; "+ bundles 3; one empty") all say three bundle slots — one cell to fix. 3:30, ten kills → 10 ✓ (the pursuit: REV104-8). **4:30 fails — REV104-6.** 6:00, the lever is powered by the tide ✓ by the district's own condition (the flats join the beacon's line only at high water; the level at which they join is asserted, not marked on the staff). 6:00, the floaters "spread on the mole" ✗ (REV104-10). 8:00, eighty join fifty at the lit flats beacon ✓. 9:00, panel to Mole: the flats beacon dies, the mole beacon lights, a hundred and thirty retarget to it ✓ — the ten floaters would too. 12:00, the third surge at the mole intake ✓ (the marker moved at 9:00). 13:30, "a full battery lost at the dock" ✗ — empty, under REV104-6. **Corrected ledger: dropped 35, collected 10, spent 10, expired 25 on the flats, 0 at the dock.**
-
### What works, and why
+
## The findings
-
- **The campaign question grows out of the answered local one.** The finale's answer — a drum turned by flowing water — leaves one observable the player has already seen: after opening R, "the thin cable that enters the relay room from outside the district still pulses on the old cadence." That is a campaign clue that costs nothing new and reframes shut/fix/hold as local outcomes, exactly as the Expansion Brief asks. Evidence changes a later action: the door to the campaign is a stopped drum that still hears time.
-
- **The six-part per-district rule is the false-refuge chain generalised**, and it carries this role's watchlist by construction: a local question with a fair chain and no item gates; one campaign clue as an inspectable stable object; what travels is a fact and a convention, never an item; one later action enabled; **redundancy — every campaign clue in two districts** — as the answer for missed clues; a consequence stated as a rule. "Or the district is a key hunt" is the right test.
-
- **The fixed contract and the may-add list** are the shared-rule contract the mechanics page demands, written by the person who owns the rules it protects: W1–W4 with precedence and the beacon definition, the light convention, the two cables, the flowing-water relay, S1–S3 fixed; new devices, topology, signal sources and beacon variants allowed with a readable signal; "may not change what power, signal or a beacon means, or make an ordinary lamp draw the Flood."
-
- **The evolving-hypotheses table** makes fairness checkable stage by stage — each wrong belief a reasonable reading, each overturned by something seen — and gives the early-stop answer at campaign scale.
-
- **Two candidate answers with their content costs**, held for the owner, and an honest risk list (the routing bank may dominate; the collector brushes clause 4; Answer B adds a presence). No new machine family is claimed.
+
### REV104-6 — The Tidal Barrier's harvest is collected from a minute away (§3.3, 4:30; load-bearing for the district)
-
### The findings
+
- **Where:** §3.3, 4:30: "From the house's step in insulation the surveyor discharges: the fifty organisms standing in it are stunned; five large motes, twenty-five units; the battery, emptied by the discharge, takes ten and fifteen expire. Battery ten again." The ground: the crowd "hold[s] at the flats beacon, on the mole's landward end"; the surveyor is in the signal house at the mole's other end; "the crossing takes a minute". Contract clause 4: "Motes fade in seconds"; Design Document §4: "walking over one adds its charge".
+
- **Why it fails:** the large motes drop where the stunned stand, at the beacon, a minute's crossing from the step, and fade before anyone can reach them. Collected is 0, not 10; the battery is empty from 4:30 to extraction; the 13:30 row loses nothing at the dock; the totals are collected 10, expired 25. It is §13's harvest with the crowd moved out of reach.
+
- **Consequence:** the district's stated lesson, "the discharge buys charge, not passage", is false in the scene written to show it — the discharge buys eight seconds and nothing else — and the tidewatcher's coil is dead weight, which collapses the loadout contrast with the runner that is the district's second criterion.
+
- **Category:** contradiction (scene versus clause 4).
+
- **Minimal change:** one beat. At 4:30 the surveyor wades in insulation to the crowd's edge on the knee-deep flats, discharges there, collects along the edge during the eight seconds (the §13 pattern) and returns to the house, with the hits and the pursuit that costs stated; then 13:30's full battery is earned. Or drop the coil from the tidewatcher and give the district a second loadout that does something else.
-
**REV104-1 — What a local dispatch requires is stated three incompatible ways (load-bearing).**
-
- *Where:* World r18: "the relay is the district's one source of signal, a drum turned by the race"; the drum's contact "makes the pulse". WLD103: after R is opened "the drum stops, local dispatches stop, and the thin cable that enters the relay room from outside… still pulses" (dispatch needs the drum); the Exchange's routing bank: "a district whose position is dark gets no announced surge until the player returns" (dispatch needs the trunk pulse); "the district relays are one network, kept in time from somewhere upstream" (the trunk keeps time). The hypotheses table's fifth row overturns "each district's relay is its own clock" — yet r18 says the pumping district's relay *is* its own clock, turned by its own race.
-
- *Why it fails:* the three behaviours are jointly consistent only if a local dispatch needs *both* the local drum's contact *and* a live trunk pulse — and that makes the trunk a second source, which r18's "one source" denies. As written, a reader cannot tell what the exchange's bank does to a district whose drum still turns.
-
- *Consequence:* the campaign's central lever and its first clue both rest on this sentence.
-
- *Category:* contradiction (r18 versus r19), within the contract the page itself declares fixed.
-
- *Minimal change:* one sentence in the fixed contract: "A district dispatches when its drum's contact closes *and* the trunk is carrying time; the drum makes the moment, the trunk permits it. Shut stops the drum; a dark bank position withholds the trunk; either alone stops announced surges." Then the fifth hypothesis row reads "each relay keeps its own time" → "each relay is permitted by upstream".
+
### REV104-7 — D023 replaces the rack and the collection rule the Campaign page and the contract are computed on (integration; PM's decision, not an error in r1)
-
**REV104-2 — The Collector's meters against clause 4 (the page's own flag).** "Charge never leaves the district" (clause 4) versus "this district's meters read what the player's rack reads: charge" taken from the mass "as it passes". The page asks the lead to resolve it as "never leaves *with the player*" or drop it. Agree; the rewording is one clause of clause 4 and belongs in the contract before any collector is designed. *Category:* contract conflict, self-reported.
+
- **Where:** PMR004 D023: "Use EQP101's eight-cell rack from the outset and shelter-selected pickup priority for the next integrated draft. Prefer this over six-to-nine capacity progression… Priority lets players deliberately ready an action instead of accidentally splitting charge." Inventory 73eb77 E1 (a fixed 2×4) and E3 ("This explicitly replaces most-room allocation"). Against it: contract clauses 4–5 (most-room; "six slots is the contract"; "about nineteen kill motes before its first discharge"); Campaign §3.1's loadouts and consequences ("the crane parts… let the workshop build the rack's third row, which is why this district is early"); §3.2's loadouts ("both assume the third row") and its 4:30 row; §3.3's loadouts (nine, with the runner drawn on six); §4 ("The rack grows once", the nineteen-motes paragraph, "the campaign's answer is heavies"); §5 ("The third rack row, from the Lock Flight's crane parts"); §7's Lock Flight consequence ("Rack row"); §10 decision 4.
+
- **Why it matters:** every rack on the page is drawn on six or nine cells and every ledger uses most-room. PMR004 §4: "New EQP rules require new examples, not reuse of the previous ledger's acceptance"; PMR005 3 already asks for the nineteen-motes rationale to be recalculated. Under a coil-first priority the tram crew's 4:30 row is not 8 / 7: the coil's battery is full five kills in, and the discharge the scene never makes becomes available — the scene changes, not only the arithmetic. And the Lock Flight loses both its refuge consequence and its stated reason for being early.
+
- **Consequence:** the pages disagree with PM's drafting baseline in the one place the criteria asked to be stated first, the contract.
+
- **Category:** contradiction between a PM decision and the current pages (integration). D023 is reversible and not owner-approved; clause 5 rightly says the owner decides the rack, and should still say so.
+
- **Minimal change:** the contract's clauses 4–5 restated under D023 with E3's rule quoted (which priority, set where, what the preview shows); then the Campaign's six loadouts redrawn on 2×4 (Collector r3 §4 shows the notation) and the three ledgers re-run under the adopted rule; then one sentence giving the Lock Flight a refuge consequence that is not the third row (COL101's one-time refits are candidates) or the crane parts a new use. Order matters: the contract first, or the ledgers are run twice.
-
**REV104-3 — A delayed first surge against W1.** "Closing a district's collector gate delays that district's first surge on the next visit." W1 says the beacon on the selected line flashes at dispatch "and the surge enters there." If the collector is empty, the drum still ticks and the beacon flashes with nothing behind it — which W1 currently forbids and which would otherwise be a fine clue ("the flash came; nothing came with it"). *Minimal change:* one clause in W1 — "a surge enters there if the collector supplies one" — and a line in the light convention for the empty flash. *Category:* missing design detail.
+
### REV104-8 — The first battery in each written expedition is filled by a beat the rules do not support (§3.1 3:30; §3.2 4:30; §3.3 3:30)
-
**REV104-4 — The contract never says what powers the district's circuit.** The panel switches "the district's one live circuit"; the coil injects; the relay is now hydraulic; but the source of the fixed power that lights beacons and opens hatches is unstated anywhere in the Design Document or on this page. Answer A supplies one — the city runs on harvested Flood charge, so shutting the head-works "turns off every powered door and pump in the city, including the colony's" — Answer B leaves it open. Either way the contract should state the source, or name it as part of the campaign question; a campaign about power cannot leave the grid unexplained. *Category:* missing design detail (contract completeness).
+
- **Where:** §3.1: the crowd "hold[s] at the quay beacon, between the surveyor and home. The surveyor is at the top of L1… The ten walkers climb the stairs in pursuit." §3.3: the crowd holds "at the flats beacon, on the mole's landward end"; "Ten walkers wade to the house's steps in pursuit" — the crossing the page itself prices at a minute. §3.2: "The crowd's front reaches the tram's step on the slope, and the surveyor holds the step with the cutter for the last of the climb: ten kills, ten motes, collected as they fall" — while the tram climbs.
+
- **Why it fails:** contract clause 3, "pursuit is local and short"; Design Document §4, "any organism within a short range of the surveyor breaks off to chase and drifts back when out of range". A basin's length and a minute's crossing are not short; ten organisms leaving a held crowd to cross the district is attraction to the surveyor, which the contract does not have (Combat R1 proposes ordering pursuit above attraction for exactly this case and keeps the range short). On the tram, motes drop on the road at the step's position and the tram leaves them; collection is walking over; nothing is collected from a moving step.
+
- **Consequence:** the coil's first charge — the beat every district's "choice it improves" waits on — is granted rather than earned in all three scenes. Collector r3 §4 shows the honest version: "the player works the rim with the cutter while the first mass gathers… it is the district's opening five minutes".
+
- **Category:** contradiction (scenes versus clauses 3 and 4), and one missing number.
+
- **Minimal change:** give pursuit range a value, or a landmark on each map (Combat asks the same); in §3.1 and §3.3 put the surveyor at the crowd's edge for the ten kills and price it in hits and time; in §3.2 kill the ten while the tram stands against the heavy and collect before it moves, or state that motes falling on the step are collected.
-
**REV104-5 — The routing bank is Finding 2 at campaign scale; price it by rule, and say what "dark" means.** The bank chooses "which district receives the next trunk pulse"; a dark district "gets no announced surge until the player returns". The page rightly flags dominance. Two sentences settle it: (a) a dark position puts a district into the Shut regime the endings table already defines — unannounced trickles that grow, a dark forecast — so "no announced surge" is never read as "no surge"; (b) the bank's price, stated as a rule before Campaign builds on it, as the panel's five-part price was: the pumping district's panel is free because lighting a branch opens its door *and* invites the surge there; the bank needs the same coupling (what does choosing a district *give* the player there, that makes withholding it a cost?). *Category:* missing design detail; future empirical uncertainty for the magnitude.
+
### REV104-9 — The new panels never say which position selects which intake, or which beacon flashes (§3.1, §3.2)
+
+
- **Where:** contract clause 3: "Each surge enters at one intake, chosen by the district's signal line: the panel's position sets the relay's lever, and at the dispatch the chosen intake's beacon flashes." §3.2: the panel "(Rail, Gates, Off)"; "Panel found Off. Forecast: first surge at 3:00, intake yard; second at 8:00, intake yard"; at 1:00 Rail lights the tram's lamp and darkens the gates; at 3:00 "sixty walkers enter the flooded yard and walk to the nearest lit beacon, which is the tram". §3.1: the panel "(Quay, Weir, Off)"; the ground names two beacons and two docks and no intake; the bargeman: "with the panel thrown to Weir the door is live and the crowd climbs the road toward the weir; the bargeman goes up ahead of it".
+
- **Why it fails:** in the pumping district Off means no pulse and entry by the sluice; here Off shows a forecast with an intake. Rail powers the rail and the lamp — which signal line does it select, and what flashes at 3:00: the yard beacon, dark under Rail, or the tram's lamp, which would make the tram a dispatch beacon with an intake wherever it stands? Gates selects which intake? In §3.1, if the panel is on Weir at the dispatch the surge enters at the weir — the top of the flight, beside the door the bargeman wants — and the road is empty, not the crowd's; the outline needs its order (the surge in at the quay, then the switch) and the intakes drawn.
+
- **Consequence:** the district built on "a beacon that moves" does not say what the moving beacon is to the signal network; the district built on "move the crowd or the water" does not say where the crowd enters.
+
- **Category:** missing design detail, in the contract's own core.
+
- **Minimal change:** for each new district, the three-row table the pumping district has — position → powered branch → intake selected → beacon that flashes — and one sentence for the tram: a lure only, which never flashes, with the yard intake and beacon keeping the dispatch, which is the reading the 3:00 beat needs.
+
+
### REV104-10 — Two sentences against the precedence (§3.3 6:00; §3.1 notebook)
+
+
- **6:00:** "those ten [floaters] spread on the mole". The flats beacon is lit and stands on the mole; clause 3: a crowd spreads "only if there is none [reachable]". They walk to it — floaters walk once the flow stops, per §3.1's 8:10 — unless floaters cannot move on stone, which the diff would then have to say.
+
- **§3.1's notebook:** "the panel cannot light [the door] without lighting the road, but the coil can". The weir beacon's circuit "energises the Head", so a discharge into the Head lights the weir beacon steady for those seconds, exactly as the coil route lights B2 in the pumping district ("'the yard stays dark' is never true of a coil route"). No crowd moves — the quay is lit and nearer — but the sentence is the §1 error PMR002 caught at REV102, and the bargeman's road depends on knowing it.
+
- **Category:** contradiction (clauses 3 and 1). **Minimal change:** two sentences.
### Minor
-
- Rule 5 (every campaign clue in two districts) is met for the exchange and the collector; the head-works' clue ("who oiled this?") is named only there. Its redundant form should be stated.
-
- The Shut regime's "trickles" and the collector's "cycled, not spawned" are the first statements of where surges come from; the contract should carry one sentence on it, since three districts now depend on it.
+
- §3.3's header slot count (above); the runner drawn on six cells in a nine-slot district (moot under D023).
+
- §3.1 uses P for the crane part; the Design Document's notation uses P for the beacon (the Campaign uses L). Say so, or change the letter.
+
- §6: "The critic's five findings on the thread (REV104-1 to -5) are the world designer's to close" — -2 and -4 were the lead's and the contract's, and all five are now answered as the table above records; replace the sentence with the status.
+
- §2.8 and §5, "The refuge as a played district", against D022 ("without a forced refuge-defence expedition"): the page already says "cut if it does not stay the same game", and D022 has provisionally cut the forced form. The next revision should say what remains — an optional home expedition, or none.
+
- §10.8 staffing is done (Team 26bb6f); the header's "not staffed" is stale.
+
- World r21 lets one clock into the colony — the dock pump's own reserve after Stop — guarded by "nothing is charged while the city's power stands". Consistent with the no-upkeep baseline because it follows the player's own act; it belongs, named, in §10.7's decision for the owner.
+
+
## What holds
+
+
The diffs are the check this role pre-registered, and three districts pass it on paper: water moved, light moved, a clock the player cannot set; none makes a lamp draw, a coil select intake or an organism shed twice. The lockkeeper and bargeman, the tram crew and tow crew, the tidewatcher and runner differ in what they do, and the runner — no battery at all — is the first rack that treats charge as a thing not to carry. The discovery chains are the six-part rule applied, with the redundant forms placed in other districts (gauges ↔ timetable; gate log ↔ intake gauge), and the consequences are rules (L2 open joins the upper canal; the gates shut dry the flats for good and put the Collector a level lower — which World r21, Collector r3 and Head-works r3 now state in the same direction). §7 marks its sketches as sketches; §8 gives no hours; §9 labels its hypotheses; §10 prices its decisions. Two ledgers close, and the one that fails does so in a way the method finds.
| A distinct problem under the shared rules — a written expedition whose choices could not occur in the pumping district | Yes: water moved; the flush | Yes: light moved; the tow | Yes: two clocks | Outline · Collector r3 yes (a held mass; three ways-on) · Head-works r3 yes (which race, which way home) |
+
| Two loadouts that differ in what they do | Yes (current vs lure); the bargeman's order missing (REV104-9) | Yes (fight vs tow) | In intent; fails as written (REV104-6) | — · yes, on D023's cells · not yet |
+
| An enemy combination with a precedence question | Flow vs light ✓ | The heavy on the rail ✓ | One body of water: charge or passage ✓ in principle | Static/Carrier merge pending (PMR005) |
+
| A discovery chain with a redundant form elsewhere | Gauges ↔ timetable ✓ | ✓ | Gate log ↔ intake gauge ✓ | Head-works' second form proposed, not adopted |
+
| A consequence stated as a rule | ✓ | ✓ | ✓ | ✓ |
| The shared-rule diff: adds, changes, signal, choice | ✓ (dry metal: contract note 3) | ✓ ("the contract says so": not yet, note 3) | ✓ | Collector's one requested W1 clause now on World r21 ✓ |
+
+
**The whole.** A map with reasons to travel and to return ✓ (§2; Districts r3 §3–§4, with returns caused, not scheduled). Early, middle and late as choices rather than numbers ✓ (§4). A colony loop without upkeep ✓ (§5; COL101's one-time refits and free departure; World r21's after-Stop clock noted above). A mystery thread with the local one's fairness ✓ (WLD103 r21; the six-part rule applied in §3). The finale as a district outcome ✓ (§2.1; World r21). Coverage and asset burden ✓ (§7). Hypotheses labelled ✓ (§9). Hours: §8 refuses a figure; Districts r3 §5 withdraws its earlier estimate and gives a beat list to attack — 34 expeditions, 8.2 hours of designed content, with overhead, deaths and hauling excluded and printed separately — which is the form this role asked for, and which stays a hypothesis wherever the owner reads it (criterion 11). Against criteria 1–11: the campaign package meets 1–10 in structure across the Campaign page and its domain pages (9's cuts and cheap alternatives in §7 and §9; 10's contradictions presented for decision in §10), and 11 in form; none is met in substance until REV104-6 to -10 are closed, and none establishes enjoyment, balance or feasibility.
+
+
## The designers' pages — conflicts with the contract only
+
+
- **Combat R1** (pursuit above attraction; role targets between them): the contract orders retarget-or-spread but not pursuit against attraction, and three of the Campaign's own scenes need the order (REV104-8). One line in clause 3, the lead's to rule.
+
- **The roster:** Campaign §4's four against CMB101's six, merging to eight — PMR004 §2 and PMR005 1 cover it. Districts r3 §10 places Combat's roles and names the floater as the Lock Flight's dependency; Enemies §0.1 adopts the floater "owned by Campaign". Consistent, once the Campaign page says so.
+
- **Collector r3:** on D023's cells, the first-discharge beat stated, charge spent locally on two named sinks, and its one requested contract clause now on World r21 — the only design page currently computed on PM's baseline. Its "held mass" row rightly claims no precedence change.
+
- **Head-works r3:** Slow merged into Keep; the water-level reversal corrected in the direction World r21 rules; the dry break and the feed named; its Stop row's "the way home always exists" matches r21's unpowered-return guarantee.
+
- **Equipment and Inventory:** E4's "no adjacency requirement" for links is consistent with the contract's silence — the Design Document drew every link adjacent and never required it; REV103's adjacency checks were of leaks, and stand. E3's example arithmetic (2 / 10 and 0 / 10, eleven pickups → 10 / 10 and 3 / 10) is right.
+
- **Colony:** no upkeep, one-time refits, free departure and return — inside the frame. "A legal six-slot equipment-only arrangement" predates D023; Equipment already caps issued cells at six of eight.
-
### Recorded for later empirical validation — not defects
+
## Recorded for later empirical validation — not defects
-
The bank's dominance once priced; the collector-gate cost; the cadence readability across districts; whether Answer B's presence changes the enemy identity the owner wants.
+
Whether a moving beacon reads at crowd density; the tide's clock against the forecast's; whether a short pursuit range makes the first battery too slow to earn; the bank's standing cost; whether eight hours of designed content is a length.
## Finding index — where every finding lives
-
Superseded reviews: [REV103 r5](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r5-retained-verbatim-superseded-by-rev104-r1) · [r4](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r4-retained-verbatim-superseded-by-rev103-r5) · [r3](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r3-retained-verbatim-superseded-by-rev103-r4) · [r2](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r2-retained-verbatim-superseded-by-rev103-r3) · [r1](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r1-retained-verbatim-superseded-by-rev103-r2) · [REV102 r6](/Hold%20The%20Flood/Design%20Review/Archive/REV102#rev102-r6-retained-verbatim-superseded-by-rev103-r1) and earlier on the REV102 archive · [REV101 r8](/Hold%20The%20Flood/Design%20Review/Archive#rev101-r8-retained-verbatim-superseded-by-rev102-r1) and earlier on the REV101 archive.
+
Superseded reviews: [REV104 r1](/Hold%20The%20Flood/Design%20Review/Archive/REV104#rev104-r1-retained-verbatim-superseded-by-rev104-r2) · [REV103 r5](/Hold%20The%20Flood/Design%20Review/Archive/REV103#rev103-r5-retained-verbatim-superseded-by-rev104-r1) and earlier on the REV103 archive · [REV102 r6](/Hold%20The%20Flood/Design%20Review/Archive/REV102#rev102-r6-retained-verbatim-superseded-by-rev103-r1) and earlier on the REV102 archive · [REV101 r8](/Hold%20The%20Flood/Design%20Review/Archive#rev101-r8-retained-verbatim-superseded-by-rev102-r1) and earlier on the REV101 archive.
| Finding | Raised in | Status |
| --- | --- | --- |
-
| REV101 Findings 1–5, Secondary 1–5, N1–N17; REV102-1 to -13; REV103-1 to -8 | REV101–REV103 | Resolved, closed, or delivered |
-
| REV103-9 — the relay's channel | REV103 r4 | **Resolved at World r18**; §11 mirror pending |
-
| **REV104-1** — what a local dispatch requires: drum, trunk, or both | REV104 r1 | **Open — load-bearing** (World, in the fixed contract) |
-
| **REV104-2** — collector meters vs clause 4 | REV104 r1 (page's own flag) | **Open** (Lead: one clause) |
-
| **REV104-3** — delayed surge vs W1's "the surge enters there" | REV104 r1 | **Open** (World: one clause) |
-
| **REV104-4** — the district circuit's power source | REV104 r1 | **Open** (Lead/World: state it or name it as the question) |
-
| **REV104-5** — the routing bank: "dark" = Shut regime; priced by rule | REV104 r1 | **Open** (World now; Campaign when staffed) |
-
-
## PM report — REV104 r1
-
-
- **Task:** REV104 (first critique of an available substantive section, per Tasks); REV103 closed. **Artifact:** Design Review, REV104 r1 (this page); REV103 r5 moved to the REV103 archive verbatim.
-
- **Reviewed:** World and Mystery 7699de in full (r18–r20 diffed against r17); Design Document ec1b6c diffed against 50046f, §13 re-tallied; PMU004's Brief, Tasks, Team, Hub and PM Reviews changes.
-
- **Changed decisions:** none by this role. Three of its own r5 pointers retracted as mid-rollout errors.
-
- **Evidence:** the quoted corrections; the tally; the quoted WLD103 sentences read against r18 and W1. No players, sessions, scores or asset checks; nothing built, prototyped, tested or created; no external source verified or repeated as fact.
-
- **Remaining risk:** REV104-1 is the sentence the campaign's lever and first clue both rest on; it should be fixed before any district is designed around the exchange.
-
- **Next handoff:** world designer — REV104-1, -3, -5 in the fixed contract; lead — REV104-2 (clause 4) and -4, and §11's mirror of r18; PM — nothing new. I critique the next substantive DES104 section as it arrives and post nothing between sections except a PM correction. **One exact PM request:** none.
+
| REV101 Findings 1–5, Secondary 1–5, N1–N17; REV102-1 to -13; REV103-1 to -9 | REV101–REV103 | Resolved, closed, or delivered (REV103-9's §11 mirror closed at DD r15) |
+
| REV104-1 — what a local dispatch requires | REV104 r1 | **Resolved at World r21** (D024); contract mirror pending |
+
| REV104-2 — the Collector's meters vs clause 4 | REV104 r1 | **Resolved at contract 69024c** |
+
| REV104-3 — the empty flash | REV104 r1 | **Resolved at World r21**; contract mirror pending |
+
| REV104-4 — the district circuit's power source | REV104 r1 | **Resolved provisionally at World r21 under D024**; contract clause 2 stale |
+
| REV104-5 — the routing bank priced; "dark" = Shut regime | REV104 r1 | **Resolved at World r21** |
+
| **REV104-6** — the Tidal Barrier's harvest collected from a minute away | REV104 r2 | **Open — load-bearing** (lead: one beat) |
+
| **REV104-7** — D023 vs the contract and the Campaign's racks and ledgers | REV104 r2 | **Open — integration** (lead: contract first, then loadouts and ledgers; the Lock Flight's consequence) |
+
| **REV104-8** — the first battery: pursuit and collection | REV104 r2 | **Open** (lead, with Combat's range) |
+
| **REV104-9** — the new panels: intake and flash | REV104 r2 | **Open** (lead: two tables) |
+
| **REV104-10** — two sentences against the precedence | REV104 r2 | **Open** (lead: two sentences) |
+
| Contract notes 1–4 — leak rate, collection, dry conductors, pointers and mirrors | REV104 r2 | Open (lead) |
+
+
## PM report — REV104 r2
+
+
- **Task:** REV104, the expanded campaign review PMR004 made Ready. **Artifact:** Design Review, REV104 r2 (this page); r1 moved to the new REV104 archive verbatim.
+
- **Reviewed:** Campaign 9d3590 in full, with per-beat ledgers on §3.1–§3.3; PMR004 and PMR005; contract 69024c against Design Document ec1b6c/5f9fbb §1, §3–§5 and World 7699de; World 9aab5e diffed against 7699de; Districts 699c8e, Collector 29ece6, Head-works 999d84, Pumping District 63d451, Enemies 0822dd, Combat 1126c3, Equipment a44990, Inventory 73eb77 and Colony a1046d for conflicts with the contract.
+
- **Changed decisions:** none by this role. D022–D024 are taken as PM's provisional drafting baseline, not as owner approval.
+
- **Evidence:** the quoted sentences and the three tallies above. No players, sessions, scores or asset checks; nothing built, prototyped, tested or created; no external source verified or repeated as fact.
+
- **Verdict:** revise — REV104-6 (one beat), REV104-7 (the D023 pass, contract first), REV104-8 (a range and three beats), REV104-9 (two tables), REV104-10 (two sentences), and the four contract notes. r1's section critique stands as delivered; no whole-campaign acceptance is offered, and none follows by inference from the closures recorded above.
+
- **Remaining risk:** REV104-7's order — if the ledgers are re-run before the contract is restated under D023, they are run twice; and the Lock Flight needs a reason to be early once the third row goes.
+
- **Next handoff:** lead — REV104-6 to -10 and the contract notes on the next Campaign and contract revisions; world designer — a second form for the head-works' clue in another district; Combat — the pursuit range as a number, for the contract; PM — nothing new. I review the resulting revisions when they exist and post nothing before then except a PM correction. **One exact PM request:** confirm that D023's rack and priority rule are the baseline the next Campaign revision is to be computed on, so the lead re-runs the ledgers once.
