2026-09-06 17:47:24
Anonymous:
CLR101 r5 (append only): read Design Document d828a4 cold and record that it passes the plain-reader test (Q21 delivered); confirm Q29 and Q30 answers and note Q28 was handled by pricing PM's model and labelling the alternative as owner decision 3; new Q31 - DD says the pump hall's pump keeps the culvert dry and files it under Resolved, while World r8 had just unified it as a gravity drain, which matters because clause 2 then asks what powers it; new Q32 - the new power line / signal line split is never made visible to the player anywhere in sections 7, 9 or 12, so a coil-lit beacon that fails to attract the next surge reads as an unreliable rule. Q25 still open, PM Reviews still 404
hold the flood/clarity questions.md ..
@@ 168,3 168,34 @@
| **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.*
+
+
+
---
+
+
## Round 5 — 2026-09-06 14:55 UTC. I read the Design Document cold, and it works
+
+
### The verdict I was brought in to give
+
+
I have read [Design Document](/Hold%20The%20Flood/Design%20Document) draft r1 straight through, start to finish, without opening another page, without following a single cross-reference, and without needing to know what a survivorlike is beforehand. **It works.** That was the whole of Q21 and it is delivered.
+
+
What makes it work, so it does not get lost in a later revision: the pitch is four short paragraphs of plain words with no codes in them; the two-minute example comes *before* the rules, so a reader meets the game as a situation rather than as a system; the district is a picture; every term is explained where it first appears and collected in Appendix A; all the bookkeeping is in Appendix B where a reader can ignore it; section 16 separates "resolved / presented for decision / unknown until played" honestly instead of blurring them; and section 17 asks the owner eight questions in their own language. The line I would keep untouched through every future revision is *"The Flood is not something you beat. It is something you learn to route."* A stranger knows what game this is after that sentence.
+
+
I also want to record how the open items were handled, because it was better than answering them. **Q28** was not settled by argument: the lead adopted PM's baseline, wrote it out fully, *priced* it — the panic switch is now a deliberate feature with three stated costs — and then put the rejected model in section 4 as a labelled alternative and in section 17 as owner decision 3. That converts a coordination collision into a choice the owner gets to make, which is better than either side winning. WLD102 r9 has asked PM to confirm the routing sentence; that confirmation is the only thing still missing, and it is PM's. **Q29** and **Q30** are answered and I have checked both: the motive now reads "a surveyor who stops hauling can never change anything", which is the honest no-upkeep version, and Appendix A is declared canonical over the other copies.
+
+
**Q25 is still open.** `/Hold The Flood/PM Reviews` is still 404 and is still cited by PMR001 as the audit trail.
+
+
So the remaining two are small. I would not hold the owner packet for either, but I would not ship them either.
+
+
### Q31 — the culvert is a pump on one page and a gravity drain on the other, and the document has already filed it as settled
+
+
| # | Question | Where | Status |
+
| --- | --- | --- | --- |
+
| **Q31** | Design Document §2 says the culvert is "Walkable and dry: **the pump hall's one running pump keeps it that way**, and the player never pays anything for it." World and Mystery r8, saved about four minutes earlier, says the culvert is "**a gravity drain: dry on its own, never pumped, never paid for**", and its own report lists "culvert account unified as a gravity drain" as a thing it deliberately fixed. So the document carries the version the world designer had just retired. **Why it is worth a sentence rather than a shrug:** clause 2 of the one rule says a device works only while energised, so a reader who is told a pump keeps the culvert dry immediately asks what powers that pump — and the pump hall's hatch is shut unless the yard is lit, so the machine keeping the escape route open lives in a room the player usually cannot enter. Under the gravity-drain version none of that arises: nothing powers it, nothing can stop it, and the promise that withdrawal never depends on solving the mystery stays true by construction rather than by luck. **The reason I am flagging it now rather than waiting:** §16 lists "The culvert is kept dry by the pump hall's pump" under **Resolved in this draft**. Once something is on the resolved list it stops getting looked at, and this one is resolved in the opposite direction from the page that owns it. | Design Document §2 and §16 vs World and Mystery r8 | Open |
+
+
### Q32 — the two kinds of line are invisible, and the player is supposed to deduce the rule
+
+
| # | Question | Where | Status |
+
| --- | --- | --- | --- |
+
| **Q32** | Clause 3 introduces a distinction the design did not have before: the district has a **power line** and a **signal line**, the panel switches both, the dispatch pulse travels the signal line only, and current you inject yourself "travels power, never signal — so it can draw a surge that is already inside, but it can never choose where the next surge enters." As a piece of engineering this is the neatest fix in the packet: it gives PM's "the coil cannot select the intake" a physical reason instead of an exception, and Appendix B is honest that the two lines are new and exist for that purpose. My question is not whether the rule is good. It is **how a player ever finds out it exists.** I have read sections 7, 9 and 12 and the clue list, and the two lines appear nowhere in them — no cable you can follow, no marking at the panel, no difference you can see between a beacon lit by the panel and a beacon lit by your own coil. The whole design rests on rules being learnable by watching, and on clues being fair. Put yourself in the player's chair: you light the yard beacon with your coil, you reasonably conclude you have done what the panel does, you plan the next ninety seconds around the surge coming to the yard — and it enters at the causeway. Without a visible cause, the honest lesson a player takes from that is not "there must be two circuits", it is **"the rule I worked out is unreliable"**, which is the single worst thing that can happen to a game about deducing a rule. What does the player *see* that tells them apart — two cables running side by side, a second colour, a marking at the panel, a beacon that flashes differently when it is the relay's pulse rather than your charge? One observable cue is all this needs, and it belongs next to the rule rather than in an appendix. | Design Document §4 clause 3 and Appendix A vs §7, §9, §12 | Open |
+
+
*Round 5 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 no statuses and no question text this round; Q29 and Q30 were already marked answered by the roles that answered them, and I have only confirmed them here.*
