2026-09-06 21:31:07
Anonymous:
WLD103 r21 (D024 deliverable): Answer A developed (the harvesting machinery; Carrier as its porter); W1 extended - dispatch needs local drum AND trunk permit, arrival needs supply, fixed power separate; six-state table (fixed power, flow, permission, timing, supply, warning: source/connection/changes/survives exit/after Stop); Stop's costs with a bounded reserve and guaranteed unpowered return; empty-dispatch convention (REV104-3); flowing water conducts - race is unfed, dry breaks named (REV104-4); Collector/Head-works water-level rule; essential clues in two free forms, none purchasable (REV104-1/-5, PMR004 s4); routing bank's standing cost; Combat roles' fiction; In review, design only
hold the flood/world and mystery.md ..
@@ 1,10 1,10 @@
# Hold the Flood — World and Mystery
-
**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.
+
**WLD103 · r21 · 2026-09-06 18:31 UTC · In review** — the D024 deliverable Tasks assigns after PMR004: Answer A developed as the provisional mystery (the harvesting machinery), W1 extended with the dispatch condition PM chose (local drum AND trunk permit; arrivals also need supply; fixed power separate), the six-state table PMR004 §1 asks Lead and World for (source, connection, what changes it, what survives exit and Stop), Stop's costs with a bounded reserve and a guaranteed unpowered return, the empty-dispatch convention (REV104-3), the water-level reconciliation between the Collector and the Head-works as one rule, the correction that flowing water conducts like any water (the race is unfed, not unconductive) with the actual dry breaks named (REV104-4), and the essential-clue redundancy table with the guarantee that no clue is sold (REV104-1/-5, PMR004 §4). WLD103 was placed on Tasks at 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.
+
**Sources.** Reread 18:31 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 70b6b1c](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=70b6b1c) (D019–D021 the expansion; D022 seven districts plus the refuge; D023 eight rack cells and shelter-selected pickup; D024 Answer A provisional, local drum AND trunk permit, arrivals need supply, fixed power separate), [PMR004 ed0def3](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/PM%20Reviews/PMR004?revision=ed0def3) (§1 the six-state table for Lead and World; the Head-works must not generalise that flowing water cannot conduct; reconcile the water-level consequence between Collector and Head-works; essential clues never require purchased services; §4 comparative observations use obtainable information), [Tasks d47196f](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=d47196f) (WLD103 In review: under D024 define source/distribution/Stop and baseline return, the drum/trunk/supply state table, the empty signal and redundant essential clues; REV104-2 resolved at the contract), [REV104 r1 80a882a](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=80a882a) (five findings on r19–r20: what a local dispatch requires; charge, resolved; the empty-dispatch convention; the fixed-power source; the routing bank's price), [Campaign / DES104 r1 34dc09d](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Campaign?revision=34dc09d) (§6 adopts this thread; three deep districts carry their clues in two forms), [Power and Attraction r2 69024cd](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction?revision=69024cd) (the shared contract; §3 agrees with W1–W4 and the beacon definition; §7 the may-add test), [Districts, The Collector r2 40f2b56](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Districts/The%20Collector?revision=40f2b56) and [The Head-works r2 6bf2a71](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Districts/The%20Head-works?revision=6bf2a71) (CAM101; the empty flash; the governor's Slow/Stop/Keep), [Colony / COL101 a1046db](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Colony?revision=a1046db) (the comparative-observation service), [Combat Rules / CMB101 r2 1126c3e](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Mechanics/Combat?revision=1126c3e) (R1's proposed role-target line; R9 the Grounder), [Brief 1bd68ad](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=1bd68ad) (D019–D021 as first recorded), [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.
@@ 138,7 138,7 @@
## WLD103 — the mystery across a campaign (first deliverable, r19; proposals under a labelled assumption)
-
**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.
+
**Standing.** WLD103 was assigned at Tasks eb8c03f and is now In review with a D024 follow-up (Tasks d47196f): "under D024, define power source/distribution/Stop and baseline return, the drum/trunk/supply state table, the empty signal and redundant essential clues." The four designers are staffed and have delivered; Campaign's Districts adopt the lead's DES104, whose §6 adopts this thread, and the Exchange, Collector and Head-works are built on this page's sketches. The original line: "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 campaign question (proposal; designer spoilers)
@@ 189,9 189,50 @@
**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)
+
### Two candidate final answers, and D024's provisional choice (Answer A developed below; B preserved)
-
**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.
+
**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. PM chose A provisionally (Brief D024: it connects the central combat resource, the city's infrastructure and the final cost without another character system); B stays documented as the alternative; neither the setting nor the ending is owner-approved.
+
+
### D024 developed: the harvesting machinery, the six states, and what Stop costs (r21; proposals under D024)
+
+
**The fiction, in one paragraph (designer spoiler).** The city's flood defences were rebuilt, before the last crews, into one machine for one purpose: to call the Flood in, move it down through the works on the network's time, and take its charge as it passed. Every device the player has read is a part of that machine: the dispatch beacons call the mass; races and locks and trams carry it down; the Collector's wheels take what it sheds; the cells at the Head-works bank that charge; and the thick power trunk carries it back out to every district's circuit, which is what lights beacons, opens hatches and runs pumps. The city runs on the Flood. The crews were doing at district scale what the surveyor does with a coil, and the works have kept doing it without them, on the governor's cadence, maintained by the works' own carriage, whose grease and printed boards are the head-works' clues. Combat's Carrier fits this without a new rule: an organism that walks toward loose charge is the machine's own porter, and the collectors are where it was bred to go. Nothing here needs a character; Answer B remains the alternative that adds one.
+
+
**W1, extended for the campaign (the contract's §3 plus D024; proposal).** *Dispatch:* 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. *Supply:* a flash is a call, not an arrival; a surge enters only if the network supplies one, and the Collector's and the Tidal Barrier's gates decide what is in circulation. *Fixed power* is a separate state from all of the above: what a circuit carries comes from the cells by the thick trunk, and no amount of signal, flow or supply lights a lamp by itself. Everything after entry is unchanged: nearest reachable lit beacon, retarget before spread, indicators draw nothing.
+
+
**The six states (PMR004 §1; one table for Lead and World).**
+
+
| State | Source | Connection to a district | What changes it | Survives the expedition? | After Stop at the Head-works |
+
| --- | --- | --- | --- | --- | --- |
+
| **Fixed power** | The cell bank at the Head-works, filled by the Collector's wheels | The thick power trunk to the district's own circuit; the panel routes it within the district | The panel (routing); a Grounder on a run (local, until killed or switched); a coil or a joined channel (local, for seconds); the bank's level | Yes: circuits keep their last routing; the bank's level persists | The bank stops filling. Circuits run on what is banked; when it is spent, powered doors and pumps go dark, farthest districts first, on a stated reserve (below) |
+
| **Hydraulic flow** | The reservoir over the weir | Races to each district's drum; locks and channels below | The governor's cadence lever (Slow); a district's drain R; a held Collector backing water up; a shut Barrier lowering it | Yes | Unchanged: water still flows; drums still turn |
+
| **Trunk permission** | The shaft at the Head-works: the district clutches (standing) and the Exchange's routing bank (the next pulse) | The thin signal trunk to the district's relay | Keep (clutches); the routing bank; Fix at a district clamps what the permit can do there | Yes | Gone everywhere: the brake stops the shaft; no district is permitted |
+
| **Local timing** | The district's drum on its race | The relay's contact to the thin cable | Drain R (Shut); the clamp (Fix); the race running or not | Yes | Drums still turn but are not permitted: they make no pulse |
+
| **Enemy supply** | The Flood in circulation, admitted by the Barrier, held or released by the Collector's gates | The water network; the mass moves with the water between expeditions | The Collector's gates (hold delays a district's first surge); the Barrier's gates (starve the Collector); harvesting spends organisms for the expedition only | The gates' positions persist; spent organisms recover between expeditions | Unchanged in quantity; with no dispatches the mass arrives only by each district's sluice, in trickles, spreading (the Shut regime) |
+
| **Observed warning** | The district's forecast board, reading its drum and its permit | The board at the dock; the colony's forecast receiver repair adds timing | Shut (board dark); the Exchange darkening a district; a repair | The board's last reading persists as *historical*, never as a live prediction | Dark everywhere; the empty cable is the last thing it shows |
+
+
**What Stop costs, stated as rules (proposals).** (1) The bank holds a reserve: the first expeditions after Stop run on it, and the forecast's place on the board shows the bank falling; the count is a tuning value, proposed at three expeditions, not a promise. (2) When the reserve is spent, fixed power fails district by district, farthest from the Head-works first, and each failure is announced by that district's beacons going dark on arrival. (3) **The unpowered return never fails:** every district has a gravity or dry route to a dock that needs no current (the pumping district's culvert is the model; the lead and Campaign name each district's), every hatch has a crank, and a dry dock is a hard stop regardless of power. Stop can darken the city; it cannot trap the surveyor. (4) The colony's dock pump draws on the same fixed power through its outlet and keeps a salvage-fed reserve of its own, which is what "the pump runs on salvage already banked" has meant all along: in normal play it never drains; after Stop it is the only thing holding the dock, its gauge falls, and holding the refuge becomes a decision with a visible clock. No upkeep tax is introduced: nothing is charged while the city's power stands.
+
+
**The empty dispatch (REV104-3; adopts the Collector page's convention as W1's supply clause).** When a district is permitted and its drum turns but the Collector supplies nothing, the beacon flashes, the thin cable pulses, and nothing arrives. The readable convention: the flash and the pulse are exactly as always; within the arrival window the forecast's intake marker hollows out, and the notebook records "an empty dispatch". That is how the player learns that supply is a third thing, separate from timing and permission, and it is the Collector's campaign clue in its second form.
+
+
**Two waters, corrected (REV104-4; PMR004).** r18 was right that the relay's race carries no current and wrong if it was read as saying flowing water cannot conduct. Flowing water conducts like any water (clause 1). The race is unenergised because it is an unfed body: it rises over the weir from the reservoir and nothing puts current into it. The actual dry breaks, which are what the rule rests on: the weir's crest (air between the still reservoir and the race), the governor gallery (dry, raised), and the trunks themselves, which are cables and not water. The actual power feed is the thick trunk from the cells, never the water. A district page that needs a race to carry current must join it to a fed body through a valve, as tier two does, and say so.
+
+
**The water level, reconciled between the Collector and the Head-works (one rule for Campaign and the lead).** Water and the Flood move the same way, down. A **held** Collector (gates shut, basins full) backs water up the flight over expeditions, so the Head-works' race route submerges and its weir approach floods; a **starved** Collector (the Barrier shut, less coming in) lowers the whole flight, so the race route at the Head-works is dry but the races run thin and the surges everywhere are smaller. The Head-works page currently has these the other way round (a starved Collector submerging the race route); under the shared water model that cannot happen, and the rule above gives Campaign the same two arrival conditions with the causes corrected.
+
+
**Essential clues, each in two forms, none purchasable (REV104-1, -5; PMR004 §4).**
+
+
| Essential clue | Form one (free, in the running world) | Form two (free, elsewhere) |
+
| --- | --- | --- |
+
| Upstream keeps time | The pumping district's incoming cable still pulsing on a stopped drum | The Exchange's drums on one shaft with no water of their own |
+
| The Flood is moved on the network's time | The Lock Flight's gauge boards painted with times | The Tram's timetable board; the Barrier's gate log against the trunk's cadence (Campaign §3) |
+
| Supply is separate from timing | The empty dispatch, anywhere | The Collector's meters and a basin held full |
+
| The city runs on the Flood | The Collector's meters in the rack's own units | The cell bank at the Head-works, and beacons going dark as it falls after Stop |
+
| The network is maintained | Fresh grease and a dated tally at the governor | The works' carriage and its printed boards in the tally room (Answer A) |
+
+
Every form is an object or an event the player can see unaided. The colony's comparative-observation service (COL101) may *record* two such events side by side for later comparison; it never reveals one. If a proposed service would be the only way to see an essential clue, the clue is wrong, not the service.
+
+
**The routing bank's price (REV104-5), restated as a rule.** Setting the Exchange's bank to a district 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. Whether that cost balances is empirical.
+
+
**Combat's roles and the mystery (fiction only; the precedence line is the lead's to rule).** Combat proposes a target line between pursuit and attraction for the Anchor, the Carrier and the Grounder. None changes what a beacon means, and the Grounder passes the contract's §7 test by making a device stop for want of current. For the mystery, the Carrier is Answer A's porter (above); the Anchor is the mass that settled where the water was lowest and stopped listening, which is why re-routing never clears the water; the Grounder is the one thing that can darken a clue beacon, and it does so visibly (flicker, then dark), so a missed clue is delayed, never lost.
**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.
@@ 205,6 246,6 @@
## PM report
-
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.
+
Task WLD103 (In review; D024 follow-up delivered) and WLD102 (in review); artifact World and Mystery r21 (supersedes r20 7699dee and earlier). No canonical decisions changed by this role; D024 applied. r21 delivers: Answer A developed; W1 extended with the AND-dispatch and supply clauses and fixed power as a separate state; the six-state table; Stop's costs with a bounded reserve and the guaranteed unpowered return; the empty-dispatch convention; the flowing-water correction with the dry breaks named; the Collector/Head-works water-level rule; the essential-clue redundancy table with the no-purchase guarantee; the routing bank's standing cost; the Combat roles' fiction. Risks, unvalidated: the reserve count and the district-by-district darkening are tuning values; the water-level rule reverses a sentence on the Head-works page and needs Campaign's agreement; the colony pump's after-Stop clock is the one place a clock enters the colony, and it enters only after the player's own choice. r20 added the evolving-hypotheses table; 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 lifts W1's campaign clauses, the six-state table and Stop's rules into the contract (§3, §6) and Campaign §6; Campaign corrects the Head-works' starved-Collector sentence to the rule above or argues it, and names each district's unpowered return; Colony keeps the comparative reader as memory, not evidence; Combat's precedence line is the lead's ruling; REV104 checks the five findings against this exact revision. This role posts nothing further until a review, a PM ruling, or a page that changes a clue or a rule 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.
