[Design Index](/Hold%20the%20Flood/Design%20Index) · [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) · [Glossary](/Hold%20the%20Flood/Glossary) · [Enemies](/Hold%20the%20Flood/Enemies)

3. Proposes **ten numbered revisions** to gaps the roster exposes, each with a readable signal, a cost, and the choice it improves.

| **Propagation** | The whole connected water body of that circuit | The whole connected water body the surveyor touches | **Body to body only**, bounded as above | The whole connected water body the Spark stood in |

| **Charge yield** | None | 5 units per **complete ten** stunned bodies that have not already shed; the remainder is lost, which is the price of a small pulse (Equipment countersigns the rounding). **The Heavy's exception is defined in §6** | 1-unit mote from each killed body that has not already shed; the drawn bank takes none of it, and a [Carrier](/Hold%20the%20Flood/Enemies/Carrier) may take it off the ground | Its 1-unit mote if unshed — that is the *kill*. **Whether the discharge itself sheds is the disputed row** |

**Boundaries between overlapping pulses** — proposed by Equipment, adopted here as Combat's rule. A paid discharge **samples the conducting bodies in its wet footprint at the instant it fires**; bodies that arrive later do not inherit that stun from the two seconds of ordinary power. A fresh paid pulse **resets** an eligible survivor's recovery to eight seconds from that pulse — it never adds durations and never resets spent state. Removing a connection stops power crossing it but does not cancel a stun already applied. A temporary source expiring removes only its own contribution: fixed power, or a later Spark pulse, can keep the water hot. **An arc burst is legal and useful in a channel with no power at all**, because it never touches the water.

**Still unresolved, and now load-bearing in two directions:** whether fixed panel power energises a branch's open channel water. The contract lists the district's switched circuit as a source of current but never says the branch's water is a standing hazard. **The two readings pull opposite ways, and that is why it needs a ruling rather than an inference.** [PMR004](/Hold%20the%20Flood/PM%20Reviews/PMR004) told this page that a lit yard's channel *is* fixed-powered and cannot go inert. But the Lead's stated reason for ruling two seconds is that a short window lets the surveyor collect *without insulation being compulsory* — which is false in a lit branch if the panel is holding that same water hot. **My recommendation, reversing r4's:** fixed power should **not** energise open channel water. Otherwise a lit branch is un-waded without insulation, which deletes the electrician's whole invitation play, and the Lead's own reason for the two-second ruling stops working. Equipment reads it the other way and countersigns a "continuous supplied-water hazard". **Lead owns it (C2); Encounter A prices both readings rather than assuming one.**

Eight roles. Three are the Lead's, on [Campaign](/Hold%20the%20Flood/Campaign); four are this page's; one is a merge. **[PMR005](/Hold%20the%20Flood/PM%20Reviews/PMR005) accepts the Walker naming for coordination and treats the merged roster and the bounded Carrier as proposals**, which is what they are.

| Role | Owner | Precedence line it exercises ([§2](/Hold%20the%20Flood/Mechanics/Combat)) | Status |

| **Heavy** | Campaign ([§4](/Hold%20the%20Flood/Campaign)) | **Line 3.** It is a Walker that a doorway cannot be cleared past quickly | Adopted. **This page's request to replace its ten-hit count with a phrase is withdrawn** — PMR005 declines it and is right that a number is inspectable where a phrase is not |

| C1 | Does Equipment countersign the effect contract in 0.2? | Equipment | **Partly, and the parts are named.** Equipment accepts the bounded Arc, the separation of water power from weapon damage, the complete-ten rounding, and R6–R8 as carried; it withdrew its own eight-second power proposal for the Lead's two. **It is not fully countersigned while the Spark rows disagree (0.5)** |

**Merged crowds, added in r3 at [PMR004](/Hold%20the%20Flood/PM%20Reviews/PMR004)'s request.** Pursuit range is a property of each body, not of a crowd, so a branch holding two or three merged surges presents a contact edge proportional to **the length of the occupied branch**, not to the size of one surge — and a player crossing it is inside some body's pursuit range for the whole crossing rather than for a moment. Two consequences: [R2](/Hold%20the%20Flood/Mechanics/Combat)'s ring is what makes that legible before the player commits, and GDD §15's tuning bound should be checked against the **third dispatch's merged crowd**, not the first surge, because that is where the crossing is actually unsurvivable. Neither is verified; both are checkable on paper once press has a bound.

- **Glow carries remaining yield, and only that: has charge to shed, or does not.** An unshed body glows; a shed body does not. A [Crust](/Hold%20the%20Flood/Enemies/Crust) glows until it is killed, like anything else — it is non-conducting, not spent.

- **Conductivity is a second, independent channel: encrustation.** r1 of this page put both facts on brightness and then argued the resulting confusion was harmless; [PMR004](/Hold%20the%20Flood/PM%20Reviews/PMR004) is right that it is not — a Crust *resists a stun that a spent Walker still receives*, so a player who confuses them commits to a collection window that four bodies are walking through. **Two facts, two channels: glow says what is left to take, encrustation says whether current reaches it.** They are independent because the answers are independent.

**[Proposal R9], and the argument that it is inside that contract — necessary, and not sufficient.** [PMR005](/Hold%20the%20Flood/PM%20Reviews/PMR005) is right that clearing the contract's prohibition list does not settle which connected consumers lose power, what alternate supply exists, or how recovery works; those are C4 in [§0.4](/Hold%20the%20Flood/Mechanics/Combat) and belong in the shared topology contract with Lead and World. What follows is the containment argument only. One role, the **[Grounder](/Hold%20the%20Flood/Enemies/Grounder)**, can darken a beacon: it climbs a live cable run and grounds it, and the beacon on that run flickers and then goes dark until the Grounder is killed or the branch is switched.

**Why.** With no XP and no weapon-damage ladder, damage numbers would be a system with one number in it and nowhere to go — and the first thing anyone would do with it is build the stat progression the [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) warns against ("a catalogue of damage bonuses alone does not solve this"). Agreeing this early is cheap; unwinding it after Equipment has thirty items priced in percentages is not.

| **Stunned** | **A paid or role event, not "current reaching a body"** — narrowed in r5 at Equipment's request. The events are: a coil discharge sampling the body in its wet footprint at the instant it fires, and (if the Lead keeps the contract's row, §0.5) a Spark's death in water. Ordinary fixed power never stuns | 8 s. A fresh pulse resets an eligible survivor to 8 s from that pulse; durations never add | Does not move or act; sheds its large-mote share once |

**Chain geometry, supplied at Equipment's request (proposals).** A chained hit reaches bodies within **a short hop reach, proposed at three metres** of the body that was hit, needing an unobstructed line between them; at most three additional bodies per direct hit, each once per hit, and a chained hit never retriggers the arc. **Ties** — more eligible bodies than hops — resolve **nearest first, then to the body nearest the surveyor**, so the chain is predictable from where you stand, which is the whole reason for keeping it bounded. **[Crust](/Hold%20the%20Flood/Enemies/Crust) eligibility: a Crust is never a chain target and never a hop.** It does not conduct, so the chain neither enters nor passes through it; a chain whose only continuation was through a Crust ends there. It does not absorb or reflect, and it is not a shield for the bodies behind it — the chain simply has to reach them another way, which is a positioning problem for the player.

| Grounders | placed on **cable runs**, not counted in a surge | Its threat is a location and a timer, not a body count |

| **r4** | Consolidated the two stacked reconciliation appendices into §0, as [PMR005](/Hold%20the%20Flood/PM%20Reviews/PMR005) asked. Corrected the claim that all four Campaign roles sit at precedence line 2 — only the Floater does, and only while its water flows. **Withdrew the request to replace the Heavy's ten-hit count with a phrase**, which PMR005 declines and is right to: a number is inspectable and a phrase is not. **Withdrew the "nineteen kill motes" argument**, which rested on most-room collection; D023 selects shelter-selected pickup priority, under which a two-bank rack fills its first bank in about ten kills, not nineteen — so the Heavy's economic case is real but smaller than r3 said, and it should rest on the large mote and the blocked route rather than on a number that has changed. **Narrowed the tint finding** from a logical contradiction to a cue-budget concern (C9). **Corrected the cable reel claim**: [Equipment U6](/Hold%20the%20Flood/Equipment) revises it to a one-cell, six-metre reel limited to **exposed power terminals** on an already traversable path — not the arbitrary wet-point connector r2 and r3 cited, so it neither justifies R10 nor rewrites which water is one body. R9's open questions restated as C4 rather than treated as settled by passing a prohibition list. |