2026-09-06 19:40:23
Anonymous:
WLD103 r19 (first deliverable, anticipated assignment under PMU004): campaign question (the district relays are one network kept in time from upstream; the pumping district's shut relay still receiving the trunk pulse is the first campaign clue); six-part rule for what every district contributes with the false-refuge fairness; fixed rule contract vs what a district may add; relay decision reframed as a local outcome; three example districts as mystery contributions (Exchange, Collector, Head-works); two candidate final answers for the owner; risks named; In review, design only
hold the flood/world and mystery.md ..
@@ 1,10 1,10 @@
# Hold the Flood — World and Mystery
-
**WLD102 · r18 · 2026-09-06 16:37 UTC · In review** — closes 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.
+
**WLD103 · r19 · 2026-09-06 16:40 UTC · In review** — the first bounded WLD103 deliverable, as scoped in r18 under a labelled assumption (the line is not yet on Tasks): 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:37 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](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review) (REV103-9 open, World first; the criteria it will apply to a cross-district mystery), [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.
+
**Sources.** Reread 16:40 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), [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.
@@ 136,13 136,48 @@
- **S2 Shelter (D1, D2 when dry, the junction platform J)** — enemies cannot enter or spawn; the surge clock runs; repacking allowed; the district stays visible.
- **S3 Live evidence** — new clues, panel switches, and their verification happen in the running world.
-
## WLD103 — the mystery across a campaign (anticipated ownership under PMU004; not yet on Tasks)
+
## WLD103 — the mystery across a campaign (first deliverable, r19; proposals under a labelled assumption)
-
**What changed.** The owner called the premise promising, rejected three to four hours of designed content as far too little, and asked for many districts (Expansion Brief, PMU004). The Expansion Brief names this role as owner of the overarching mystery and clue logic; the Design Index says World expands beyond the local mystery under WLD103; the Pumping District page pairs CAM101 with WLD103. Tasks has not yet carried the line, and the Campaign designer is proposed, not staffed. This page proceeds under a labelled, reversible assumption: that WLD103 will be assigned substantially as the index describes, and that a first bounded contribution now helps DES104 more than waiting for the line.
+
**Standing.** PMU004 names this role owner of the overarching mystery and clue logic; the Design Index and the Pumping District page pair it with CAM101 under WLD103; Tasks has not yet carried the line and the Campaign designer is proposed, not staffed. This section is written for the lead's DES104 and for Campaign to build routes and enemies against, under the assumption that WLD103 is assigned substantially as the index describes. 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.
-
**Bounded first deliverable (next revision, r19; about two pages).** (1) The overarching question the whole campaign asks, stated so that every district's local answer is a partial answer to it, with the pumping district's false refuge and relay as the first two partial answers. (2) The rule for what a district contributes: one observable local clue, one inference that changes a later action in *another* district, and the evidence that travels with the player (notes, a sign convention, a device state), under the same fairness the false-refuge chain has: a free experiment, a recovery path if missed, an answer for replays. (3) The relay decision reframed as a district outcome with campaign-wide consequences for dispatch, forecast and travel, not the ending of the game. (4) The world rules that must stay identical everywhere (W1–W4, the light convention, the two cables) versus what a district may add, so that Campaign and Combat can propose combinations against a fixed contract. (5) Three contrasting example districts sketched only as mystery contributions, one paragraph each, for the Campaign designer to build routes and enemies on, not as district designs. Not in scope: district counts, hours, enemies, equipment, colony economy.
+
### The campaign question (proposal; designer spoilers)
-
**Assumptions and the PM decision this needs.** The pumping district remains the opening district; the shared rule contract is the Design Document's §4 as of r13 plus this page's W1–W4; the four proposed designers do not exist yet, so this contribution is written for the lead's DES104 and adopted or corrected by Campaign when staffed. **PM request:** confirm WLD103's scope as above or redirect it, and say whether the campaign question should be answered in the minimum campaign or left open for a later owner decision.
+
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.
+
+
The first campaign clue is already in the pumping district and costs nothing new: **after the player shuts the relay (opens R), the drum stops, local dispatches stop, and the thin cable that enters the relay room from outside the district still pulses on the old cadence.** Something upstream is still keeping time. That reframes the finale exactly as the Expansion Brief asks: shut, fix and hold are local outcomes, persistent for this district, and the incoming pulse on a stopped drum is the door to the campaign.
+
+
### What every district contributes (the rule; the false-refuge chain is the model)
+
+
Each district's mystery page states these six things, or the district is a key hunt:
+
+
1. **A local question the place itself asks** (as the signed refuge asked one), answered inside the district by observable clues, a fair inference, a free experiment available on the first visit, a consequence, a recovery path if the clue is missed, and an answer for replays. No item gates.
+
2. **One campaign clue:** an observable, stable object (W3) that only makes full sense with evidence from another district: a drum with no race that still ticks; a tally board whose marks match another district's cadence; a signal cable leaving toward a named place. It is inspectable in three or four lines, never a lore paragraph.
+
3. **What travels with the player:** a fact in the notebook and a convention the player now reads everywhere (as W4 made turned signs readable district-wide). Nothing travels as an item that gates a door.
+
4. **One later action it enables, in another district or on a return:** for example, having read the exchange's drums, the player can predict a district's next intake without its forecast relay; having shut one relay, the player can hear whether the trunk still ticks there.
+
5. **Redundancy:** every campaign clue appears in two districts in different forms, so a missed clue is recoverable without a guide and the campaign never depends on one room.
+
6. **A consequence stated as a rule:** what this district's persistent outcome (its relay state, a gate left open, a collector closed) does to another district, the refuge, or a return visit.
+
+
### What stays fixed everywhere, and what a district may add (the contract for Campaign and Combat)
+
+
**Fixed in every district, or the campaign's knowledge stops being knowledge:** W1–W4 with the retarget-or-spread precedence and the definition of a beacon; the light convention (steady, flashing, dark; wet and dry by tint); the two cables and the rule that only a flashing beacon chooses an intake; the flowing-water relay as the district's one source of signal; S1–S3. **A district may add,** with a readable signal and a choice it improves: new powered devices (doors, pumps, wheels, lifts) on the same clause; new water topology (races, pools, weirs, drains) that changes what conduction reaches; a second signal source, or none; more than two fixed beacons; planted-beacon variants. **A district may not** change what power, signal or a beacon means, or make an ordinary lamp draw the Flood.
+
+
### The relay decision as a district outcome (reframed; replaces "ends the game")
+
+
Shut, fix and hold keep the consequences in the endings table above, for this district, persistently. They no longer end the game. Shut adds the campaign clue (the incoming pulse on a stopped drum). Fix, clamping the lever, also clamps what the upstream pulse can do here, which is why the upstream network matters. Hold records the choice. The campaign-scale version of the same choice belongs at the head-works (below), and whether the campaign answers its own question or leaves it to a later owner decision is PM's call, asked in r18.
+
+
### Three example districts, as mystery contributions only (one paragraph each; Campaign designs the district)
+
+
**The Exchange.** Where signal cables from several districts meet: a hall of drums ticking together, all turned by one shaft that enters from a race the player cannot see the head of. Local question: why do these drums have no water of their own? Campaign clue: one shaft, one time source; the pumping district's incoming pulse comes from here. Travels: the trunk's cadence and which cable goes where. Enables elsewhere: the exchange has a routing bank, a panel with one position per district, so the player can choose which district receives the next trunk pulse; a district whose position is dark gets no announced surge until the player returns. Consequence as a rule: setting the bank changes another district's forecast before the player arrives there. Redundant clue: the pumping district's stopped drum still ticking.
+
+
**The Collector.** The low place the water drains to, and where crowds go between expeditions: basins with wheels turned by the mass moving through them, and meters on the wheels. Local question: why does the Flood come back every time? Campaign clue: the city moves the Flood as it moves water, and takes something from it as it passes (this district's meters read what the player's rack reads: charge). Travels: the fact that the surges are cycled, not spawned, and the sign convention the crews used at drains. Enables elsewhere: closing a district's collector gate delays that district's first surge on the next visit, at the price of the collector filling. Consequence as a rule: a closed gate is a persistent district state with a visible cost in the collector. Redundant clue: the exchange's shaft turns faster when a collector is full.
+
+
**The Head-works.** The reservoir whose flow turns every race, and the governor that regulates it: fresh grease on the governor, a tally board with today's date, a lever with more positions than any panel. Local question: who oiled this? Campaign clue: the network is maintained, not merely running. Travels: the answer to the campaign question, in one of two forms below. Enables elsewhere: the campaign-scale choice. Consequence as a rule: the head-works' state changes every district's dispatch at once.
+
+
### Two candidate final answers, for the owner (proposals; neither is chosen here)
+
+
**Answer A, the machine:** nobody is left; the governor is maintained by the city's own automatic works, and the last crews were doing at district scale what the player does with a coil, stunning and harvesting the Flood to keep the city's power on. The Flood is what the city runs on. The choice at the head-works is the relay-room choice at scale, and shutting it turns off every powered door and pump in the city, including the colony's. **Answer B, the keepers:** someone still lives at the head-works and keeps the network in time on purpose, steering the Flood away from where they are and toward the districts the player has been crossing, which is why the refuge routes are the overrun ones. The choice at the head-works is then whether to stop them, join them, or take the lever. A does not need a new enemy or character; B needs one presence and a reason. Both keep the Flood massed enemies and never water, and both are reachable through the same devices. Which the campaign answers, and whether it answers at all, is the decision PM asked for in r18.
+
+
**What this costs in content.** No new machine family: drums, races, cables, valves, wheels, meters, tally boards and signs recur; each district adds topology and one or two devices. The asset burden per district is the pumping district's, minus what recurs; the readable states are the same table with new rows for meters and the routing bank. No availability is claimed.
## Content and asset burden
@@ 154,6 189,6 @@
## PM report
-
Task WLD102 (in review) and WLD103 (anticipated); artifact World and Mystery r18 (supersedes r17 26f497b and earlier). No canonical decisions changed by this role. r18 closes 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. Next from this role: r19, the WLD103 first deliverable as scoped above, unless PM redirects it first; the Document needs the weir clause and the flowing-water sentence in §11. 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.
+
Task WLD103 (anticipated; first deliverable) and WLD102 (in review); artifact World and Mystery r19 (supersedes r18 d1d56a7 and earlier). No canonical decisions changed by this role. r19 delivers 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.
