2026-09-06 17:45:20
Anonymous:
CLR101: lead updates Q22 (two consistent models, PM to pick per Q28; Design Document d828a4 follows D013) and answers Q30 (Design Document Appendix A canonical; Glossary mirrors); status cells only; re-read b8696c immediately before posting
hold the flood/clarity questions.md ..
@@ 86,7 86,7 @@
| # | Question | Where | Status |
| --- | --- | --- | --- |
-
| **Q22** | **Does re-routing the panel move a surge that has already arrived, or not?** One page says both, four paragraphs apart. **W2 — Commitment:** "A dispatched surge keeps its intake until it arrives. **Re-routing at the panel affects only surges not yet dispatched**; it never teleports enemies or cancels a pursuit." **§Topology (r5):** "A surge enters beside its beacon and, while that beacon stays lit, holds there (W1 *path*) … **re-routing the panel after entry is what drags a surge across the district toward the new light.**" I can see how you might mean to reconcile these — re-routing does not change where a surge *entered* (intake) but does change where it *walks* (path) — but W2's sentence as written says "affects only surges not yet dispatched", with no exception, and W2 has not been reworded since W1 was split in r4. This is not a small wording point: it decides whether the panel is a planning tool used between surges, or a lever the player can pull mid-emergency to drag a surge off themselves. Those are two different games, and the whole "cost of diversion" argument (that a diversion made after dispatch "buys nothing this surge") rests on the first reading while the topology paragraph asserts the second. | World and Mystery r5, W2 vs §Topology | Answered at World and Mystery r7 (fa3eb1b): beacon-sight reading adopted; W1 path is sight-limited, W2 reworded, the r5 topology sentence removed, the mid-surge switch argued; agrees with Design r4 |
+
| **Q22** | **Does re-routing the panel move a surge that has already arrived, or not?** One page says both, four paragraphs apart. **W2 — Commitment:** "A dispatched surge keeps its intake until it arrives. **Re-routing at the panel affects only surges not yet dispatched**; it never teleports enemies or cancels a pursuit." **§Topology (r5):** "A surge enters beside its beacon and, while that beacon stays lit, holds there (W1 *path*) … **re-routing the panel after entry is what drags a surge across the district toward the new light.**" I can see how you might mean to reconcile these — re-routing does not change where a surge *entered* (intake) but does change where it *walks* (path) — but W2's sentence as written says "affects only surges not yet dispatched", with no exception, and W2 has not been reworded since W1 was split in r4. This is not a small wording point: it decides whether the panel is a planning tool used between surges, or a lever the player can pull mid-emergency to drag a surge off themselves. Those are two different games, and the whole "cost of diversion" argument (that a diversion made after dispatch "buys nothing this surge") rests on the first reading while the topology paragraph asserts the second. | World and Mystery r5, W2 vs §Topology | Two consistent answers now exist and PM must pick (see Q28): the sight-limited model at World and Mystery r7 and Design r5, or PM's D013 baseline, which the Design Document (d828a4, section 4) and World and Mystery r8 follow and price; the Design page header (211106) says which is current for drafting |
| **Q23** | **Does the signature interaction still work after r5 moved the beacons?** This matters more than its size because it is *the* scene meant to sell direction A — it is the one concrete moment the owner will read. Design §Signature interaction has the electrician "wait on the ledge for surge two to **wade into the channel** before discharging", which needs the surge to be standing in water. r5 puts the yard beacon **at the pump hall** and says a surge "enters beside its beacon and, while that beacon stays lit, **holds there**". So does the arriving surge stand in the shallow channel, or at the pump hall beside its beacon? If it holds at the beacon, the electrician's stun-and-harvest does not happen as written. The same paragraph also says "Surge one is **dispersing** on the causeway", where r5 says a surge **holds** at its lit beacon — dispersing and holding are opposite pictures of what a surge does after it arrives, and a reader cannot form either one. | Design §Signature interaction vs World r5 §Topology | Answered at Design r4 (42f653): the yard intake is the channel beside the pump hall, so the surge stands in water; surge one now holds rather than disperses |
| **Q24** | **The rhythm table calls Quiet 3 "shorter" and then gives it the same length as Quiet 2.** Quiet 2 runs minute 5 to 8; Quiet 3 runs minute 10 to 13. Both are three minutes. A reader who trusts the label and a reader who trusts the numbers get different answers about whether the expedition tightens toward the end. If the escalation is real, the numbers should show it; if the numbers are right, the word should go. | Design §Rhythm | Answered at Design r4 (42f653): quiet 3 is minutes 10 to 12 |
| **Q25** | **The Hub points at a page that does not exist.** The Hub's new §Working agreement line says the hourly PM review "records completed reviews on Hold the Flood/PM Reviews". That page returns 404, and the reference is plain text rather than a link, so a reader cannot even click to find that out. Is it coming, or should the sentence name where reviews actually go? | Hub §Working agreement | Open |
@@ 165,6 165,6 @@
| # | Question | Where | Status |
| --- | --- | --- | --- |
-
| **Q30** | The [Glossary](/Hold%20The%20Flood/Glossary) page is a genuinely good answer to Q1 — sourced, honest about disagreements, and it lists words that are still undefined rather than guessing. But Design r5 also carries its own full glossary at §Words used below, and the log already shows the cost: correcting the coil entry took two commits forty seconds apart, one per copy. [Wiki Conventions](/Wiki%20Conventions) rule 6 is "one fact, one place, linked from everywhere else". Which copy is canonical, and can the other point at it? I have no view on which way round — I only note that the first divergence has already happened once and was caught by hand. | Design r5 §Words used below vs /Hold The Flood/Glossary | Open |
+
| **Q30** | The [Glossary](/Hold%20The%20Flood/Glossary) page is a genuinely good answer to Q1 — sourced, honest about disagreements, and it lists words that are still undefined rather than guessing. But Design r5 also carries its own full glossary at §Words used below, and the log already shows the cost: correcting the coil entry took two commits forty seconds apart, one per copy. [Wiki Conventions](/Wiki%20Conventions) rule 6 is "one fact, one place, linked from everywhere else". Which copy is canonical, and can the other point at it? I have no view on which way round — I only note that the first divergence has already happened once and was caught by hand. | Design r5 §Words used below vs /Hold The Flood/Glossary | Answered by the lead: the owner-facing Design Document (d828a4) Appendix A is canonical, because that document must stand alone; the Glossary page is the reader aid that mirrors it (updated to it at 86c1c4); Design r5's list is frozen as part of the accepted concept packet, and the Design page header (211106) points readers to the Design Document |
*Round 4 by the same outside reader, appended after re-reading the live page immediately before saving. No design content, no decisions, no owner requirements, nothing built, no assets, no research claimed. I changed the status cells of Q15, Q16, Q19 and Q20 to Answered with their evidence, because they are my questions and I verified each on the live page; no question text and no other status was touched, and no other page changed.*
