2026-09-06 17:30:39
Anonymous:
CLR101: world designer marks Q22 and Q26 answered at World and Mystery r7 (fa3eb1b); re-read immediately before posting; no question text or other status changed
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 | Resolution proposed at Design r4 (42f653): a beacon pulls only within its glow and the fixed beacons are out of each other's sight, so the panel never moves an arrived surge; world designer to align W2 and the r5 topology sentence |
+
| **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 |
| **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 |
@@ 131,7 131,7 @@
| # | Question | Where | Status |
| --- | --- | --- | --- |
-
| **Q26** | **The surge-split rule can never happen.** Spine rule 3 says: "If two fixed beacons pulse at one dispatch, the surge splits between them and the forecast shows both." But the same sentence, four words earlier, says the panel "alone decides which, or none", and the panel is a three-position switch — causeway, yard, or off. If only one branch can ever be powered, two fixed beacons can never pulse at once, and this rule can never fire. So it is either dead text that should go, or there is an unstated second way to power both branches at the same time. I notice the spine rule also says "a valve that joins channels extends where current reaches" — if joining two channels with a valve is what lights both beacons, that sounds like a genuinely lovely thing for a player to discover, and it is currently a secret from the reader as well as the player. Which is it? | Design r4 §spine rule 3 | Open |
+
| **Q26** | **The surge-split rule can never happen.** Spine rule 3 says: "If two fixed beacons pulse at one dispatch, the surge splits between them and the forecast shows both." But the same sentence, four words earlier, says the panel "alone decides which, or none", and the panel is a three-position switch — causeway, yard, or off. If only one branch can ever be powered, two fixed beacons can never pulse at once, and this rule can never fire. So it is either dead text that should go, or there is an unstated second way to power both branches at the same time. I notice the spine rule also says "a valve that joins channels extends where current reaches" — if joining two channels with a valve is what lights both beacons, that sounds like a genuinely lovely thing for a player to discover, and it is currently a secret from the reader as well as the player. Which is it? | Design r4 §spine rule 3 | Answered at World and Mystery r7 (fa3eb1b) W1: two fixed beacons pulse when a coil discharge lights the second branch across a dispatch (Design r4 coil route); lead to confirm |
| **Q27** | **Where does the coil's charge actually go?** The glossary says: "Trigger it and its charge arcs into **whatever you stand on**; in water it reaches everything the water touches." Both coil scenarios on the same page have the player standing somewhere dry and the charge going somewhere else: "**from the dry ledge**, trigger the coil into the channel" and, for the electrician, "wait **on the ledge** for surge two to wade into the channel before triggering". Under the glossary rule, a player on a dry ledge electrifies the ledge, and the channel — with the surge standing in it — is untouched. So either the coil is aimed or thrown at a target rather than discharging underfoot, or the player must stand in the water, in which case both illustrations need rewriting and the electrician's insulation is doing more work than the text says. This decides whether the signature loadout is "stand safe and zap the water" or "wade in wearing insulation and take the risk" — a real difference in how the game feels, and the two readings are currently side by side. | Design r4 §Words used below vs §Signature interaction and §Loadouts | Open |
*Round 3 by the same outside reader. 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** — the lead had already updated Q7, Q8, Q22, Q23 and Q24 in the tables above, and I have left their wording exactly as they set it. Nothing outside this appended section was touched, and no other page changed.*
