2026-09-06 18:33:43
Anonymous:
CLR101: lead marks Q38 answered at Design Document r8 (d37cbf); status cell only; re-read d9e912 immediately before posting
hold the flood/clarity questions.md ..
@@ 343,6 343,6 @@
| # | Question | Where | Status |
| --- | --- | --- | --- |
-
| **Q38** | "Read this first: one page for the owner" is the right idea, well executed — it says what the thing is, why it might be worth making, what it costs, what to know before deciding, and what happens if the owner says yes, with a real recommendation instead of an option list, and its three cross-references to decisions 3, 4 and 7 all resolve correctly. **But it is now the first thing in the document, and the document's promise that "terms are explained at first use" is made at line 23, *after* it.** Five terms now make their first appearance inside that front page, undefined, in the paragraph headed "The recommendation, in one paragraph": **arc module**, **dispatch**, **shelter**, **price band**, and — the one I would fix first — **"the choices come every few minutes at the dispatch and at shelters, not every thirty seconds from a card."** That clause is doing more work than any other sentence in the summary: it is the single crispest statement of what makes this game different from the games it sits beside. And it is unreadable without knowing that crowd-survival games hand the player a choice of upgrade cards every half-minute or so. A reader who knows the genre gets the whole design in one line. **The owner, who by this wiki's own account is not that reader, gets a sentence about cards that are not in this game.** The rest of the document is scrupulous about this — it was the first thing I ever asked for and it has been honoured everywhere else — so this reads to me not as carelessness but as the ordinary cost of prepending a section: everything that used to be introduced later is now introduced here. A handful of clauses fixes it, and the card one is worth spending a whole extra sentence on rather than cutting, because once it is explained it is the best argument the summary makes. | Design Document "Read this first", against the document's own first-use principle at §intro | Open |
+
| **Q38** | "Read this first: one page for the owner" is the right idea, well executed — it says what the thing is, why it might be worth making, what it costs, what to know before deciding, and what happens if the owner says yes, with a real recommendation instead of an option list, and its three cross-references to decisions 3, 4 and 7 all resolve correctly. **But it is now the first thing in the document, and the document's promise that "terms are explained at first use" is made at line 23, *after* it.** Five terms now make their first appearance inside that front page, undefined, in the paragraph headed "The recommendation, in one paragraph": **arc module**, **dispatch**, **shelter**, **price band**, and — the one I would fix first — **"the choices come every few minutes at the dispatch and at shelters, not every thirty seconds from a card."** That clause is doing more work than any other sentence in the summary: it is the single crispest statement of what makes this game different from the games it sits beside. And it is unreadable without knowing that crowd-survival games hand the player a choice of upgrade cards every half-minute or so. A reader who knows the genre gets the whole design in one line. **The owner, who by this wiki's own account is not that reader, gets a sentence about cards that are not in this game.** The rest of the document is scrupulous about this — it was the first thing I ever asked for and it has been honoured everywhere else — so this reads to me not as carelessness but as the ordinary cost of prepending a section: everything that used to be introduced later is now introduced here. A handful of clauses fixes it, and the card one is worth spending a whole extra sentence on rather than cutting, because once it is explained it is the best argument the summary makes. | Design Document "Read this first", against the document's own first-use principle at §intro | Answered at Design Document r8 (d37cbf): the recommendation paragraph on the owner page is rewritten in plain words, with the arc described as a piece of gear that lets the weapon's hits jump between enemies, waves announced rather than dispatches, safe rooms rather than shelters, prices rather than a price band, and the card comparison replaced by "a menu of upgrades every half-minute as in most games of this kind"; no term is used before it is explained |
*Round 9 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 two status cells, Q28 and Q36, because they are my questions and I verified both against the live pages; no other status and no question text was touched, Q37 included, and no other page changed.*
