**WLD103 · r20 · 2026-09-06 16:41 UTC · In review** — WLD103 is now on [Tasks eb8c03f](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=eb8c03f) (Ready) and Brief D019–D021 record the owner's expansion; r20 adds the one element the formal line asks for that r19 only implied, the player's evolving hypotheses, and maps the line to this page's sections. r19 was the first WLD103 deliverable, written minutes before the line under a labelled assumption: the campaign's overarching question, the rule for what every district contributes to it with the false-refuge chain's fairness, the fixed rule contract against what a district may add, the pumping district's relay decision reframed as a local outcome that is also the first campaign clue, three example districts sketched only as mystery contributions, and two candidate final answers left for the owner. Written for the lead's DES104 and for the Campaign designer when staffed. r18 closed REV103-9 (the relay's channel carries *flowing* water, not energised water: the relay is the district's one source of signal, a drum turned by the race above the weir, so the valves can never light the yard from the relay's side, and R stops the drum without touching the district's power), and records the owner's expansion direction (PMU004) as it bears on this role: the overarching mystery and clue logic across a campaign of districts, WLD103, anticipated but not yet on Tasks; the bounded first deliverable is scoped at the end. r17 was the targeted revision PMR003 requested of this role: the three valves' found and set positions and the success condition (connectivity, not order) in one table; the relay's own supply against the door's, and what drain R stops and leaves working, with one added clause (R sits above the head valve's weir, so it empties only the relay's feed); the access chain's consequence qualified by route (a crowd held by a still-lit causeway beacon stays put on the coil route); the Shut row's workshop claim removed. The lead's r13 proposals for these are confirmed here with that one addition, so [Document r13 50046f7](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=50046f7) needs only the weir clause to match. r16 merged the tier-three chain with the one the lead proposed in [Design Document r9 fb6b6df](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=fb6b6df) "for the world designer to correct and own", so there is one chain, on this page, for §11 to lift: the lead's access chain (the crew's note as a three-valve sequence that joins the yard's water to the sluice head) followed by this page's relay chain (drum, lever, clamp, drain valve). Two reconciliations are stated in the PM report. r15 was the revision PMR002 requested of this role (items 1 and 3): W1 now says what counts as a beacon and the precedence between retargeting and spreading; the junction lamp is an indicator, not a lure; a state table checks the three signature routes and the failed experiment against the rule as written; tier three gets a complete clue → inference → action → consequence chain, an endings table with each ending's dispatch, retreat and colony consequence, no salvage price on the choice itself, and the early takeaway Q36 asked for. r14 applied PMU002's rulings: the title moves out of "owner requirements" to its D017 status as the owner-supplied working title (Clarity Q37 was right); D016 confirms the routing baseline, so the standing decision request is closed; D015 seats the five further contributors on the Team, so their pages are cited as team work, and REF101's electrofishing reference is cited as research grounding for W1. No rule or chain text changed. r13 aligned two tier-two sentences to [DES102 draft r6 12779dc](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=12779dc), which states the critic's REV102-6 on the document's own principle: any current in the joined water energises the junction circuit, so with the valve open the panel lighting the yard is enough to open the junction gate, at the price of a hot yard; with the valve shut, a coil discharge into the pool opens it quietly; the coil buys stealth, not access. Nothing else changed from [r12 23dca93](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=23dca93), which aligned to draft r4, whose r3 topology stands (the lead's r4 note and REV102 issue 1 both settle on this page's r10 choices). r12 re-instated r10's body, undoing [r11 eac7ed8](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=eac7ed8), which had aligned to draft r2 while r3 was aligning to r10. To make a third crossing impossible, this page no longer carries its own map: topology and crowd behaviour are sourced from the Design Document's sections 2 and 4 and only summarised here with a notation key; this page remains the source for W1–W4 and the mystery chain, which the document's section 9 mirrors. Any topology change starts here and is agreed before either page moves, as the lead's r3 note asks. [r10 c6f0598](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=c6f0598), [r9 41681d9](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=41681d9), [r8 ba6f8b8](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=ba6f8b8) and earlier are page history. Author: World and Mystery Designer. Handoff: canonical Lead (D014) for DES102; PM. WLD101 was accepted in PMR001 as a concept contribution (at [r6 4302067](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=4302067)); [r7 fa3eb1b](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=fa3eb1b) and earlier revisions are page history.

**Owner requirements.** Survivorlike; exploration, experimentation, mystery; the Flood is massed enemies (Brief D011); Unity; Steam; assume nothing exists. "Hold the Flood" is the owner-supplied working project title, not a recorded requirement; final naming is the owner's and is not locked (Brief D017). Design only until the owner explicitly authorizes development after reviewing the design document (D007). No AI-generated art; prefer verified free assets; purchases and rare authored assets need owner approval. This revision creates no assets, code, prototypes, or tests. Bioelectric enemies, the drowned district, the small colony, and every rule below are proposals, not owner approvals (D013).

**Sources.** Reread 16:41 UTC: [Brief 28fb1c2](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=28fb1c2) (D013 provisional A; D014 canonical lead; D015 five owner-added contributors seated; D016 routing baseline confirmed; D017 working title; D018 criterion 11), [Tasks 1370285](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=1370285) (PMU002: WLD102 In review at r12; DES103 Ready for the lead; this role checks clue/rule changes against the exact integrated revision), [Team cbf8d79](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Team?revision=cbf8d79), [PM Reviews a2beab4](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/PM%20Reviews?revision=a2beab4), [PMR002 2199471](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/PM%20Reviews/PMR002?revision=2199471) (items 1 and 3 assigned to this role; delivered in r15–r16), [PMR003 72c692e](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/PM%20Reviews/PMR003?revision=72c692e) (reviewed World r16; finale machinery credited; targeted revision on valves, supplies, drain, coil-route targets and the workshop claim), [Tasks 6e92d0c](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=6e92d0c) (WLD102 In review, targeted revision; REV103 Ready), [Document r13 50046f7](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=50046f7) (lead's proposals for the same items, confirmed here), [Expansion Brief 1a568e4](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Expansion%20Brief?revision=1a568e4) (PMU004: the owner called the premise promising, rejected three to four hours as far too little, and asked for many districts; this role owns the overarching mystery and clue logic; four designers proposed, not staffed), [Design Index 3cc078d](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Index?revision=3cc078d) (World expands beyond the local mystery under WLD103), [Pumping District 655b140](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Districts/Pumping%20District?revision=655b140) (CAM101 with WLD103), [REV103 r5 205bfb1](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=205bfb1) (the criteria it will apply to a cross-district mystery: the false-refuge chain as the model; evidence that changes a later action; the same fairness), [Brief 1bd68ad](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=1bd68ad) (D019 owner expansion supersedes the one-district scope; D020 domain pages plus a concise owner document; D021 four designers proposed, not staffed), [Tasks eb8c03f](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=eb8c03f) (WLD103 Ready: central question, evolving hypotheses, evidence across districts, later knowledge enabling a return, fail-safe essential clues, a campaign payoff; relay ending as local resolution; coordinate geography with Lead and Campaign), [Expansion Prompts ed17df8](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Team/Expansion%20Prompts?revision=ed17df8) (Campaign owns geography, travel, order and district pages and must coordinate the global mystery rather than add key hunts; World owns the overarching mystery, clue logic and enemy fiction; Combat, Equipment and Colony own their systems), [Tasks 95db055](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=95db055) (WLD102 Ready: revision requested), [Design Document r9 fb6b6df](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=fb6b6df) (DES103 r3: PMR002 item 1 done on the document in parallel with r15 and in agreement with it: precedence stated once in §4, the junction lamp an indicator, coil-lit beacons steady and never flashing, the failed experiment rebuilt around the Off position; item 3: a tier-three access chain proposed for this page to own, merged here), [Design Document r8 d37cbf0](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=d37cbf0), [Design Review REV102 r5 e2db8b9](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=e2db8b9) (revise: the arc; nothing to this role), [Design r5 b030c98](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design?revision=b030c98), [Design Review r6 a892274](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=a892274), [Design Review r7 bb68711](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=bb68711) (closes Finding 2 under the sight-limited model; N17), [Clarity Questions b8696cc](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Clarity%20Questions?revision=b8696cc) (Q28 on the crossed saves; Q29 marked answered at r8 by this role), [PM Reviews 04f3183](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/PM%20Reviews?revision=04f3183) (PMR001 checkpoint; next review prioritises WLD102), [Glossary f1bf1f4](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Glossary?revision=f1bf1f4), [External Critique 319c975](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/External%20Critique?revision=319c975) (EXT101; the External Critic is a team member since D015; its X9 on the title is answered by D017 and on this page by r14), [Design Document r6 12779dc](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document?revision=12779dc) (r5 bc134bf states REV102-6 and adds the one-page owner summary; r6 merges owner decisions 4 and 6 with measured market data; r4 46b320b sections 2, 4, 9, 11 and Appendix B read; r3 d35209f aligned to this page's r10), [Design Review REV102 r2 82a96ba](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=82a96ba) (all five r1 issues verified resolved; verdict: ready for owner review as the base of DES103; one residual, REV102-6), [Design Review REV102 r1 4dde90c](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=4dde90c) (verdict: revise, one bounded pass; issue 1 recommends this page's r10 topology; issue 3 the flash observable), [Disagreement Register 8dd233c](https://open-wiki.tail2e4d02.ts.net/Disagreement%20Register?revision=8dd233c) and [Reference: Survivorlike Market Data 39c95f2](https://open-wiki.tail2e4d02.ts.net/Reference/Survivorlike%20Market%20Data?revision=39c95f2) (The Troll and the Reference Researcher, team members since D015; Q37 on the title came from the register and is answered here), [Design r6 211106d](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design?revision=211106d) (header note: rules now maintained on the Design Document), [Glossary 86c1c4e](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Glossary?revision=86c1c4e). No comparative research and no asset verification.

**What r8 did.** PMR001 chose the simpler routing model over the sight-limited one that r7 and Design r4–r5 had adopted: **the panel alone selects the intake at dispatch; after entry every surge continuously follows the nearest reachable energised beacon, district-wide.** r8 rewrites W1/W2, the map, the chain, the price of the panel, and both required scenes under exactly that model, removing r7's glow-range and split-surge text. It reconciles the culvert account (no pump; item 6), re-derives the dock-choice consequence (item 2), and supplies the motive, tiers, and ending without upkeep and without making the Flood water (item 5). Word definitions stay in [Design's glossary](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design#words-used-below); the wiki editor's Glossary mirrors it. The sight-limited model is recorded once, at the end, as a set-aside alternative.

North is the interior; the docks are south. `=` raised and dry, `~` shallow water, `-` the culvert (a gravity drain: dry on its own, never pumped, never paid for).

The map is drawn once, in the [Design Document, section 2](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Document#2-the-district) (draft r4, from this page's r10, and not re-drawn on either page again). This page uses short labels for it: **D1** causeway dock (held dry by default) · **D2** yard dock (flooded by default; wet, conducts) · **P** the panel at the causeway head · **B1** causeway beacon at the causeway's far end · **I1** causeway intake beside it · **B2** yard beacon at the pump-hall door · **I2** yard intake, the channel mouth at the door, in water · **H** the pump-hall hatch, on the yard circuit with B2, hand crank inside · **X1, X2** the culvert's exits at the two dock ends (a gravity drain, always dry, never paid for) · **J** the junction platform, a shelter · **GJ** the junction gate into the interior, on the junction's own circuit, which the panel never reaches by wire; any current in the junction pool energises it: with valve **V** open the pool is joined to the yard channel, so a lit yard is enough, and with V shut a coil discharge into the pool opens it quietly · **S** the sluice beside the junction, the Flood's own way in. Shelters (S2 hard stops): D1, D2 when dry, J. The causeway has no device; what lighting it buys is the road and where the next surge enters. H blinks and closes when its branch loses power, never on an occupant, and can be cranked open from inside in ten seconds; that is the hall's recoverable exit.

- **W1 — Attraction.** *Intake:* at each dispatch the relay fires one pulse down the branch the panel selects: *Causeway* (B1 pulses, the surge enters at I1), *Yard* (B2, I2), or *Off* (no pulse; the surge enters at the sluice). Only the relay pulses. A beacon lit by local current (a coil discharge into a channel, or a valve joining the two branches' water) glows steady and lures, but never pulses and never changes the next intake: the relay's output is a separate line from the lamp (the Design Document's thin signal cable beside the thick power cable, both switched by the panel). This is visible, not a hidden rule: at a dispatch the pulse is seen running the thin cable and the beacon flashes; a coil-lit or planted beacon glows steady and never flashes. **Only the beacon that flashes chooses an intake, and nothing the surveyor carries can make a beacon flash.** *What counts as a beacon (r15, PMR002 item 1):* exactly three devices lure: the two fixed beacons B1 and B2, and the portable beacon module. Every other lamp, including the junction pool's lamp, the panel's indicators, and any hatch light, is an indicator that shows a circuit's state and draws nothing. *Path:* after entry a surge moves continuously toward the nearest reachable lit beacon anywhere in the district, fixed or planted, panel-lit or coil-lit. *Precedence, stated once:* a crowd keeps its current lit target unless another lit beacon is nearer, or its target goes dark; when its target goes dark it retargets to the nearest reachable lit beacon if there is one, and only with none reachable does it spread along the branch it is in (from the sluice, along the interior route and then both branches). Lighting a beacon farther from a crowd than its current lit target moves nothing. The panel needs no item, slot, resource, or notebook flag; what it costs is stated under "The price of the panel".

- **W2 — Commitment (entrance only).** A dispatched surge keeps its intake: nothing changes where it came in, and nothing teleports it. Switching the panel changes which beacons are lit, and therefore where every entered surge walks next. The forecast shows the next dispatch's intake as a map marker that moves the moment the panel changes, a locked marker for a surge already dispatched, and each entered surge's current target beacon.

**How a surge behaves once it has arrived (item 2).** It gathers around its target beacon and holds there while that beacon stays lit and no lit beacon is nearer; each surge is larger, so the held crowd's radius grows, and by surge 3 the causeway's far end or the channel mouth is full. Two things move organisms besides beacons, in the Design Document's terms: **pursuit range** (any organism within a short range of the surveyor breaks off to chase and drifts back when out of range, which is what the cutter fires at) and **press** (the gathered crowd's edge creeps slowly outward along its branch during the quiet interval, so "quiet" means a moving line you can read, not an empty branch; stragglers roam between surges; the next surge re-concentrates it). A surge whose beacon goes dark retargets to the nearest reachable lit beacon if one exists and otherwise spreads along its branch at once, both ways (W1 precedence). What creates survival decisions while a crowd holds: the hatch, the richest deposits, and the motes all sit at the far ends where the crowd is, and the press brings its edge toward the dock ends; harvesting or opening anything means working at the crowd's edge inside its pursuit range, or waiting and losing surge time.

Switching is free of resources and available on expedition one. It is paid, visibly, five ways:

1. **Exposure.** P stands in the open at the causeway head, a dash from D1 and R1. Switching with the countdown near zero means being on, or next to, the branch you just lit.

5. **Commitment.** The intake is fixed at dispatch; a switch after dispatch changes where the surge goes after it enters, never where it enters, so the forecast's locked marker stays true.

**Where the coil fits.** A coil discharged into the yard channel lights B2 steady and opens H for the seconds the charge lasts, without touching the panel: a lure and a key, not an intake. B2 and H share a circuit, so "the yard stays dark" is never true of a coil route: the yard glows, it does not flash. A crowd moves to B2 only if B2 is nearer than its current lit target or its target is dark; the panel's next intake is unchanged, because only the flashing beacon chooses it.

Proposed play, not a playtest. Light convention: steady = powered, pulsing = the relay dispatching, dark = unpowered.

| Step | Evidence, inference, consequence |

| Infer | Power is key and lure at once: the lit branch is where a door opens, where the next surge enters, and where every crowd walks. The refuge sign marks where the Flood is sent. Someone kept the culvert and the yard in use by leaving the panel on Causeway. |

| Discover | The causeway's far end empties as the crowd crosses; the next dispatch enters at the channel mouth. The hall is open, and both the old crowd and the new surge are coming to it. Reaching the answer below costs exactly that. |

| Act | Open the three valves in the table below (only connectivity matters, not order); light the yard at the panel, or discharge the coil in the pool; watch the sluice-head lamp light when the water is joined. |

| Understand | The relay is the one device in the district that *makes* signal instead of consuming power: its race, the sluice-head channel above the weir, flows past a wheel that turns the drum, and the drum's contact makes the pulse. It runs on flowing water, not energised water; there is no current in that race, and its wheel is visible turning. The drum decides *when*; the lever decides *where*. Nothing else is new: a drain valve empties a channel (the field pump did the same in the yard), a clamp fixes a lever, and the door beside the room obeys the same rule as a hatch. |

| Act | **Shut:** open R. **Fix:** set the lever, then clamp it. **Hold:** leave the room as found and record the choice at the dock. Each is one interaction; none consumes salvage; the cost was reaching the room. |

| **Shut** | No dispatches; the forecast board is dark. The Flood arrives only by the sluice, on an unannounced timer, as trickles that grow over the expedition, never as an announced surge; with no lit beacon to reach they spread along the interior route and then both branches. Beacons, hatches and the panel still work: a lit beacon still draws whatever is inside. | Keep their targets; nothing new enters by the branches. | The expedition still ends at fifteen minutes and the docks are still hard stops, so withdrawal is by the culvert as ever, with nothing to read but the crowd itself. Observation replaces the forecast: the honest, harder district. | The held-dock choice matters less (no announced intake to keep off it); the forecast relay repair is spent; the workshop stays useful. |

| **Hold** | Unchanged. | Unchanged. | Unchanged. | The colony knows the relay could have been stopped and was not; the board records it. |

**Early, middle, final (illustrative; the expedition count is a proposal, not coverage).** Early: the panel, the culvert, the yard; hauler loadouts; the first colony repair. Middle: G and the interior; valves; the held-dock switch; electrician and shepherd loadouts; the tally board and the inked route. Final: the relay room and the choice. A rough twelve to twenty expeditions is the lead's number to defend in DES102 against the content above; this page supplies the tiers, not the count.

Nothing is open for this role. Draft r3 aligned to this page's r10 and applied its items 1–7 (gravity-drain culvert and dead pump; both docks share the bypass and the asymmetry is water; the press-rate bound as a tuning constraint; each crowd's target on the forecast; the turned-sign rule; the relay room by valve sequence, not a key; the chain rows lifted). Draft r4 completed REV102 issues 3 and 5 (the flash observable, now mirrored in W1 and the Understand row above; the bound restated in section 15) and settled the topology. r11's two items were overtaken: r3 chose *press* and *pursuit range* and the three-part dock cost. Division of sources from here: the Design Document's sections 2 and 4 are canonical for topology and crowd behaviour; this page is canonical for W1–W4 and the mystery chain, which section 9 mirrors; if they drift, the drift is reported here and fixed in one place, and no topology change is made on either page before it is agreed on this one.

- **S3 Live evidence** — new clues, panel switches, and their verification happen in the running world.

**Standing.** WLD103 is assigned (Tasks eb8c03f, Ready): "expand the local mystery into a campaign thread: central question, evolving hypotheses, evidence across districts, later knowledge enabling a meaningful return, fail-safe essential clues and a campaign payoff; reassess the current relay ending as local resolution; coordinate campaign geography with Lead and the proposed Campaign designer." Where each is answered: the central question, below; evolving hypotheses, the table added in r20; evidence across districts and later knowledge enabling a return, the six-part rule and the three examples; fail-safe essential clues, rule 5 (every campaign clue in two districts); the relay ending as local resolution, its own subsection; the campaign payoff, two candidate answers held for the owner, with PM's ruling requested. Geography is Campaign's; this section names only what a district must contribute. The Campaign designer is proposed, not staffed, so this is written for the lead's DES104 first. Everything in it is a proposal; the Flood's identity and the setting stay open, and nothing here needs a specific enemy. Not in scope: district counts, hours, enemy roles, equipment, colony economy.

The pumping district asked "why is the marked refuge overrun?" and answered it locally: the last crew steered the Flood with the district's own relay. Its finale asked "what calls the Flood?" and answered: a drum turned by flowing water. The campaign asks the question those two answers open: **the district relays are one network, kept in time from somewhere upstream; what, at its head, is still keeping time, and for whom?** Every district's local mystery is a partial answer to that question, and the evidence for it is the same machinery the player already reads: drums, races, the thin signal cable, tally boards, turned signs.

One district reused before and after discovery: two docks, causeway, culvert, yard, pump hall, junction platform, sluice, interior and relay room, one panel, two fixed beacons, two devices, a forecast overlay, a tally board and plan, one valve, and wear and sign props (one sign rotated for W4). Evidence types: light state, cable path, wear, a turned sign, an unlabelled panel, a map marker, a crowd's visible target. No compatible free asset set or terms are verified; plain-text inspection is the fallback for props; readable live crowd cues are the lead's Finding 5 table. No custom asset creation is proposed.

r7 and Design r4–r5 used a sight-limited path (a beacon pulls only within its glow) so that the panel could never move an arrived surge. PMR001 set it aside for the simpler district-wide rule above, priced honestly, and PMU002 confirmed that choice after considering the alternative (Brief D016): one visible change has a direct consequence in an existing crowd, and the separate dispatch signal preserves entrance predictability. The decision is made for this draft and remains open to an argued revision; the sight-limited wording is in [r7](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/World%20and%20Mystery?revision=fa3eb1b), and the Design Document presents it as the labelled alternative and owner decision 3. **This role's position, since a register on this wiki notes that nobody has stated one:** if asked, prefer the sight-limited model, for the reasons given in r7 item 3 (a planning-tool panel keeps the forecast marker always true, keeps the mystery's fairness independent of where a shepherd stands, and needs no panic-switch pricing); the district-wide model is consistent and honestly priced, and the difference is which game the owner wants at the panel. This page is on D013/D016; the preference is recorded, not applied, and a future argument can reopen it.

Task WLD103 (Ready on Tasks eb8c03f; first deliverable submitted) and WLD102 (in review); artifact World and Mystery r20 (supersedes r19 71c8d59 and earlier). No canonical decisions changed by this role. r20 adds the evolving-hypotheses table the formal line asks for and maps the line to the page; r19 delivered the WLD103 first deliverable as scoped in r18: the campaign question, the six-part contribution rule, the fixed contract versus district additions, the relay decision reframed as a local outcome that is also the first campaign clue, three example districts as mystery contributions, and two candidate final answers for the owner. Risks, unvalidated: the exchange's routing bank is a campaign-scale panel and may dominate travel decisions unless Campaign prices it; the collector's charge reading brushes clause 4 (charge never leaves the district) and must be resolved by the lead as "never leaves with the player" or dropped; Answer B adds a presence the design has avoided so far. r18 closed REV103-9 with one readable exception stated once (the relay is a source of signal driven by flowing water in a race above the weir; nothing electrical is in that water; the valves join the pools only below the weir) and scopes WLD103's first bounded deliverable with its assumptions and one PM request. r17 delivered PMR003 item 2 in full: the valve table with found and set positions and the connectivity success condition; the two supplies and drain R's effect, with the weir clause that keeps the pools and the yard channel wet; the coil-route qualification; the workshop claim removed. The lead's r13 proposals are confirmed rather than replaced, so the document needs only the weir clause. r16 merged the lead's r9 tier-three access chain with this page's relay chain into one chain for §11 to lift, with two reconciliations: (a) **Shut** keeps the fifteen-minute expedition and the docks as hard stops (the lead's version; r15 had removed the window); (b) **Fix** clamps the signal cable only, so the intake is fixed and power still switches, and the lead's "welded branch's door open forever, the other's shut forever" is dropped, because under the two-cable rule a clamp on the lever cannot fix the power line. r15 delivered: item 1's check as a state table (the failed experiment's written outcome does not follow from the rule; the correct failure is stated; "the yard stays dark" is false of any coil route), W1's beacon definition and retarget-before-spread precedence, the junction lamp settled as an indicator; item 3's complete tier-three chain, the endings table with dispatch, retreat and colony consequences, the ending's salvage cost removed, and Q36's early takeaway. r14 applied PMU002's rulings; no rule and no chain text changed there. r13 aligned the tier-two door to Design Document r6 / REV102-6 (two sentences). r12 aligned to Design Document r4, mirrors its flash observable in W1 and the chain, removes this page's duplicate map in favour of a link and a notation key, records that nothing from REV102 r1 or the r1–r3 checks remains open for this role, and states this role's position on the routing model without changing the applied baseline. r8 delivered: items 1 and 2 (W1/W2 under PM's model; map; crowd behaviour; the five-part price of the panel; re-derived dock-choice consequence; both scenes; hatch-closure and recoverable-exit rule; culvert account unified as a gravity drain, item 6) and item 5 (motive without upkeep; title kept and related to holding enemies off the refuge; three tiers and an ending on the existing district). Evidence: written reasoning against Tasks ee938e6, Brief 3cf14c7, Design b030c98, Design Review a892274; no player data. Risks, unvalidated: a live-lever panel may dominate if the crossing route and shut door are too cheap; crowd thinning and proximity radius are balance levers with no numbers; readable crowd targets on a crowded screen. Handoff: none open to the lead from this page; the Design Document's section 9 may re-lift the Understand row from r12 if it wants the notation to match. Handoff: the lead's r9 already carries the precedence, the indicator lamp, the steady coil-lit beacon and a rule-obeying failed experiment (built on the Off position; a different scene from this page's state table, and both obey W1, so the document's is canonical); §10's salvage sentence is already corrected. What remains for the lead is one clause in §11 (drain R above V3's weir empties only the relay's feed) and the Shut row's workshop wording, already correct there; REV103 can read the valve table and the supplies paragraph as the rule text behind §11. Handoff: lead, for DES104's mystery thread and for §11 (the weir clause, the flowing-water sentence, and the finale as a local outcome with the incoming pulse); Campaign, when staffed, builds districts against the six-part rule and the fixed contract; PM confirms or redirects WLD103's scope and answers the two questions in r18. This role posts nothing further until PM's ruling, a DES104 draft, or a review addresses it. For REV103: the precedence rule and the endings table are new rule text and should be read against §4 and §13. Risks, unvalidated: the shut ending's unannounced trickle may be too quiet or too cruel without a forecast; the fix ending's "safer, not safe" depends on the same press bound as expedition one.

**Routing decision: answered.** Brief D016 confirms D013 after considering the sight-limited alternative; this page has been on D013 since r8, so nothing changes, and the standing request in r9–r13 is closed. The External Critique and the other four contributions are team work since D015; REF101 is cited above as research, EXT101's title finding is answered by D017 and this revision.