Commit 430206

2026-09-06 17:16:45 Anonymous: WLD101 r6: plain-language definitions and in-fiction answers for Clarity Questions Q4/Q7/Q8/Q9/Q13/Q14 (proposals); reword culvert; flag stale Tasks (Q15) and unrecorded CLR101 author to PM; no rule changed; In review, design only

hold the flood/world and mystery.md ..
@@ 1,12 1,12 @@
	# Hold the Flood — World and Mystery
-	**WLD101 · r5 · 2026-09-06 14:06 UTC · In review** — supersedes r4 (e54d6a3), r3 (c92838c), r2 (438f1bf), r1 (01378d), all in page history. Author: World and Mystery Designer. Handoff: Lead (DES102), Independent Design Critic (DES102 review), PM. PM accepts.
+	**WLD101 · r6 · 2026-09-06 14:16 UTC · In review** — supersedes r5 (33dc2ae), r4 (e54d6a3), r3 (c92838c), r2 (438f1bf), r1 (01378d), all in page history. Author: World and Mystery Designer. Handoff: Lead (DES102), Independent Design Critic (DES102 review), PM. PM accepts.
	**Owner requirements.** Survivorlike; exploration, experimentation, mystery; the Flood is massed enemies (Brief D011); Unity; Steam; assume nothing exists. Design only until the owner explicitly authorizes development after reviewing the design document. 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.
-	**Sources.** Reread 14:06 UTC: [Hub](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood), [Brief a449b2](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=a449b2), [Tasks 254220](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=254220), [Design db8c5c3](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design?revision=db8c5c3) (DES101 r2 plus integration notes 1–3; note 3 confirms the W1 split and adopts the r4 topology), [Design Review 3fd6dfc](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=3fd6dfc) (REV101 r4: concept-packet review complete, verdict "ready for OWN101"; N10 raised against W1's path clause; r3 698c13 and r2 47d51da retained). PM has not yet recorded a working direction (OWN101 open); no Design Document page exists. No comparative research and no asset verification. Setting, enemy identity, and every mechanic below remain proposals.
+	**Sources.** Reread 14:16 UTC: [Hub](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood), [Brief a449b2](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Brief?revision=a449b2), [Tasks 254220](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Tasks?revision=254220), [Design db8c5c3](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design?revision=db8c5c3) (DES101 r2 plus integration notes 1–3; note 3 confirms the W1 split and adopts the r4 topology), [Design Review 3fd6dfc](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Design%20Review?revision=3fd6dfc) (REV101 r4: concept-packet review complete, verdict "ready for OWN101"; N10 raised against W1's path clause; r3 698c13 and r2 47d51da retained), [Hub f55be6b](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood?revision=f55be6b) (PM 75c3c3c records an owner-approved hourly PM review and a notification policy; a later one-line link was added by a reader), [Clarity Questions cc0ee73](https://open-wiki.tail2e4d02.ts.net/Hold%20the%20Flood/Clarity%20Questions?revision=cc0ee73) (CLR101 r1, by a "Naive Design Reader" not on the recorded Team; treated as reader feedback, not an assignment). PM has not yet recorded a working direction (OWN101 open); no Design Document page exists. No comparative research and no asset verification. Setting, enemy identity, and every mechanic below remain proposals.
-	**Revision history.** r1: the false-refuge chain and W1–W3 in a setting-neutral relay district. r2: mapped onto DES101 A; withdrew r1's clock-freezing observation view for S1–S3. r3: answered the lead's integration note and REV101 r1 (W1 dispatch-instant, W4 turned signs, unlabelled panel with forecast marker, reachable answer, four-part cost of diversion). r4: answered REV101 r2 and integration note 2 (W1 split into intake and path; sluice as Off intake; second dock). **r5:** fixes REV101 N10, the one open item on this page: W1's path clause said *pulsing*, which is undefined between dispatches; it now says *energised*, evaluated continuously, and states what a surge does with no energised beacon reachable. r5 also places each branch's beacon at its far end from the docks and gives the three-line no-panel extraction trace the critic asked DES102 to show, because it tests this page's "withdrawal never requires solving this" claim. Everything else is r4 text.
+	**Revision history.** r1: the false-refuge chain and W1–W3 in a setting-neutral relay district. r2: mapped onto DES101 A; withdrew r1's clock-freezing observation view for S1–S3. r3: answered the lead's integration note and REV101 r1 (W1 dispatch-instant, W4 turned signs, unlabelled panel with forecast marker, reachable answer, four-part cost of diversion). r4: answered REV101 r2 and integration note 2 (W1 split into intake and path; sluice as Off intake; second dock). **r5:** fixes REV101 N10, the one open item on this page: W1's path clause said *pulsing*, which is undefined between dispatches; it now says *energised*, evaluated continuously, and states what a surge does with no energised beacon reachable. r5 also places each branch's beacon at its far end from the docks and gives the three-line no-panel extraction trace the critic asked DES102 to show, because it tests this page's "withdrawal never requires solving this" claim. Everything else is r4 text. **r6:** adds one section of plain-language definitions and in-fiction answers for the Clarity Questions that touch this page's words and narrative meaning (Q4, Q7, Q8, Q9, Q13, Q14), written so the owner-facing document can lift them; replaces "dry without payment" with plain wording in the topology. No rule changed.
	## World rules — proposal for DES102, aligned to the spine rule
@@ 17,7 17,7 @@
	- **W3 — Stable evidence.** Wiring, signs, wear marks, and signal behaviour are identical on every expedition. Water states, pumps, enemies, loose salvage, and surge timing may vary or reset (DES101 r2 persistence list) and can change the best route, never the rule.
	- **W4 — Turned signs.** Every refuge sign in the district that has been turned faces the way the last crew actually went. First seen in the culvert (facing the yard); confirmed by the reachable answer below; thereafter a navigation clue wherever the prop recurs. Same sign asset, rotated. Under W3 it never changes.
-	**Topology (one statement; r4 adds the sluice and the second dock for N3 and N4).** Two docks at the district's rim: the *causeway dock*, held dry by default, and the *yard dock*, flooded by default and unusable until the colony's pump holds it dry instead (DES101 r2's exclusive choice; while flooded it is wet ground and therefore conducts). Between them the raised dry causeway, signed as the evacuation route, beacon live by default; the culvert beneath it, dry without payment, with cart wear and a turned sign; the pump hall and salvage yard beside a shallow channel, beacon dark, hatch on the yard circuit. At the district's low end, where the two branches meet, the *sluice*: the Flood's own way in, no beacon, opening straight onto the interior route. Each branch's beacon stands at its far end from the docks: the causeway beacon at the causeway's interior end, the yard beacon at the pump hall. A surge enters beside its beacon and, while that beacon stays lit, holds there (W1 *path*), so the overrun "refuge" is the causeway's interior end and the dock end stays passable; re-routing the panel after entry is what drags a surge across the district toward the new light. Three intakes: Causeway, Yard, and the sluice when the panel is Off. Panel resets to *Causeway*; the first dispatch follows a short scouting interval the lead sets.
+	**Topology (one statement; r4 adds the sluice and the second dock for N3 and N4).** Two docks at the district's rim: the *causeway dock*, held dry by default, and the *yard dock*, flooded by default and unusable until the colony's pump holds it dry instead (DES101 r2's exclusive choice; while flooded it is wet ground and therefore conducts). Between them the raised dry causeway, signed as the evacuation route, beacon live by default; the culvert beneath it, dry on its own (no bundle has to be spent on a pump to keep it dry), with cart wear and a turned sign; the pump hall and salvage yard beside a shallow channel, beacon dark, hatch on the yard circuit. At the district's low end, where the two branches meet, the *sluice*: the Flood's own way in, no beacon, opening straight onto the interior route. Each branch's beacon stands at its far end from the docks: the causeway beacon at the causeway's interior end, the yard beacon at the pump hall. A surge enters beside its beacon and, while that beacon stays lit, holds there (W1 *path*), so the overrun "refuge" is the causeway's interior end and the dock end stays passable; re-routing the panel after entry is what drags a surge across the district toward the new light. Three intakes: Causeway, Yard, and the sluice when the panel is Off. Panel resets to *Causeway*; the first dispatch follows a short scouting interval the lead sets.
	**No-panel extraction trace (for DES102's written expedition; illustration, not a playtest).** First expedition, panel untouched on *Causeway*, causeway dock held dry. Surge 3 enters at the causeway's interior end and holds at its lit beacon. The player at the yard takes the culvert back under the causeway to its dock-side exit, then the short open stretch to the dock, an S2 hard stop. Nothing on that route is on the surge's path unless the player lit something else. So "withdrawal never requires solving this" holds on paper by construction, not by timing; whether the open stretch is comfortable is empirical.
@@ 72,10 72,24 @@
	**Replay after the answer.** The question closes; the decision does not. The same three dispatches, the same panel, and a different rack, cargo target, and held dock make the routing choice fresh each expedition. Diverting never creates extra enemies or rewards.
+	## Plain words and fiction — answers to Clarity Questions that touch this page (proposals)
+
+	CLR101 r1 was added by a reader who is not on the recorded Team; nothing in it is an assignment, and this page has not edited that page (PM's hourly review may record statuses). These answers cover only the words and fiction this page owns and are written to be lifted into the owner-facing document without cross-references. The lead owns coil, rack, cutter, bundle, charge, mote, and health (Q5, Q6, Q10, Q11).
+
+	- **Expedition (Q4).** One trip from a dock into the district and back, ending at a dock or in rescue. This page uses only "expedition"; the Brief's "run" means the same thing.
+	- **Surge.** One large wave of the Flood entering the district. Three per expedition, each larger.
+	- **Intake.** A place where a surge can enter the district: the causeway's far end, the pump hall, or the sluice.
+	- **Beacon.** A fixed lamp at a branch's far end, on the district's circuit. Lit steady means its branch is powered. It flashes once when a surge is released, and that flash is what the surge comes to.
+	- **Panel.** The switch at the causeway head that sends the district's one live circuit to the causeway, to the yard, or to nowhere.
+	- **Dispatch (Q7).** The district's relay still runs on its old timer. At each scheduled tick it fires one pulse down whichever branch is powered; it was built to call crews and pumps to that branch, and the Flood answers it the same way. So a dispatch is a timer tick: nothing is sending the Flood on purpose now, and the last crew learned to point the pulse (the tally board). Automated, not haunted; once run by someone, now left running.
+	- **Forecast (Q8).** The relay's own schedule, read from its board at the docks: when the next tick fires and which branch is powered, therefore where the surge will enter. The player has it because the district always had it; it is the Flood's timetable only because the Flood follows the pulse. The colony's "forecast relay" repair restores the dock's reader so the first tick is known before departure. The timer's cadence is the lead's to vary; W3 lets timing vary, never the rule.
+	- **Causeway, culvert, sluice, hatch (Q9).** Causeway: the raised dry road from the dock into the district, signed as the way out. Culvert: the drain tunnel under it, walkable, dry on its own. Sluice: the low gate where water, and the Flood, come in when nothing calls them elsewhere. Hatch: a door that opens only while its branch is powered.
+	- **Why the player is there, and the title (Q13, Q14; proposal, not a setting lock).** The colony is the handful of people living on the one dock the pump keeps dry. Salvage is what runs that pump and mends the dock; stop bringing it back and the dock floods, and the district's last dry ground goes under. "Hold the Flood" then reads literally: not fighting the mass, but holding the water and the mass off the one place that still stands, by learning to send them elsewhere. The surveyor's question, why the machinery was turned against the Flood, is how they learn to do that. If the owner prefers another title or motive, nothing else on this page depends on this paragraph.
+
	## Content and asset burden
	One district reused before and after discovery: two docks, causeway, culvert, yard, pump hall, sluice, one panel, two beacons, one hatch, a forecast overlay, a tally board and plan, and a handful of wear and sign props (the sign reused rotated for W4). Evidence types: a light state, a cable path, wear marks, a turned sign, an unlabelled three-position panel, a map marker. No compatible free asset set or terms are verified; plain-text inspection is the fallback for any prop that cannot be sourced. No custom asset creation is proposed; any would need owner approval first.
	## PM report
-	Task WLD101; artifact World and Mystery r5 (supersedes r4 e54d6a3). No canonical decisions changed. Changed proposals: W1 path clause now *energised*, continuous, with a no-beacon default (closes REV101 N10); beacon placement at each branch's far end; the no-panel extraction trace. Evidence: written analysis of Design db8c5c3 and Design Review 3fd6dfc against Brief a449b2; no player data. Risks, all unvalidated: the shepherd's standing lure may dominate corridor defence; *Off* as a trap for new players unless the forecast marker shows the sluice as clearly as the branches; the open stretch between culvert exit and dock is where the withdrawal claim will actually be felt. This page has no open items from REV101 r1–r4; this role posts nothing further until a DES102 draft exists or PM records a direction. Next handoff: lead carries W1–W4 (with N10 fixed here), S1–S3, and the r5 topology into DES102; critic reviews DES102; this role checks the integrated draft for contradictions when it exists. **PM request:** record the working direction (A, B, or premise change) and whether W1–W4 and S1–S3 are carried into DES102 as candidate rules. No acceptance or development authorization is assumed.
+	Task WLD101; artifact World and Mystery r6 (supersedes r5 33dc2ae). No canonical decisions changed. r6 adds definitions and fiction for Q4, Q7, Q8, Q9, Q13, Q14 as proposals; r5 closed REV101 N10 (W1 path clause), placed beacons, and gave the no-panel extraction trace. Evidence: written analysis of Design db8c5c3, Design Review 3fd6dfc, and Clarity Questions cc0ee73 against Brief a449b2; no player data. For PM: the reader's Q15 is accurate — Tasks 254220 still shows WLD101/DES101 "Ready" and REV101 "Waiting for first submission" while the pages are at r6/r2+3 notes/r4 — and CLR101's author is not on the recorded Team; this role has not treated the page as an assignment and asks PM's hourly review to decide whether to adopt it. The Hub's new notification policy (owner notified only for decisions, approvals, milestones, blockers) is acknowledged. Risks, all unvalidated: the shepherd's standing lure may dominate corridor defence; *Off* as a trap for new players unless the forecast marker shows the sluice as clearly as the branches; the open stretch between culvert exit and dock is where the withdrawal claim will actually be felt. This page has no open items from REV101 r1–r4; this role posts nothing further until a DES102 draft exists, PM records a direction, or a PM review addresses this page. Next handoff: lead carries W1–W4 (with N10 fixed here), S1–S3, and the r5 topology into DES102; critic reviews DES102; this role checks the integrated draft for contradictions when it exists. **PM request:** record the working direction (A, B, or premise change) and whether W1–W4 and S1–S3 are carried into DES102 as candidate rules. No acceptance or development authorization is assumed.