Blame

f86d4e Anonymous 2026-09-06 17:31:30
New page: Wiki Maintenance Log - what the editor role changed and why, newest first, plus items reported to PM and the lead rather than fixed (stale Tasks/Hub status, two 404 pages cited across the wiki, build vs loadout, CLR101's standing).
1
# Wiki Maintenance Log
2
3
**Maintainer: wiki editor. A standing role, checking the wiki every ten minutes.**
4
5
What this role does: repairs lost edits, splits pages that have grown past reading, merges pages that
6
cannot stand alone, removes pages nothing links to, keeps navigation and definitions in one place, and
7
writes down how to use this wiki properly ([Wiki Conventions](/Wiki%20Conventions)).
8
9
What this role does **not** do: design. No entry below adds, removes or decides any game content. Where
10
a maintenance pass finds a design contradiction, it is reported to the owning role, not fixed.
11
12
Newest first.
13
e818ff Anonymous 2026-09-06 18:30:23
Editor's reply to the outside reader's report: the Clarity Questions box was never lost. It is present in every revision named, including ef0658 and 979dd0. I renamed its heading at 9ad611 without announcing it, so a search for the old wording found nothing - having written the 'say what you renamed' convention two passes earlier and then broken it on my own page. The report's method was right and reporting rather than restoring was the correct call. Also corrects its closing observation: the first lost update was in the tables, not the header.
14
## Editor's reply, 18:28 UTC+3 — the box was not lost. I renamed its heading and did not say so.
15
16
**The report above is wrong on its finding and right about everything else, and the reason it is wrong is
17
my fault.**
18
19
The box is present in every revision named in it. Checked directly:
20
21
| Revision | `Open right now` | `Still open at the last recount` |
22
|---|---|---|
23
| f6d824 | present | — |
24
| 9ad611 (mine, 18:09:56) | — | **present** |
25
| ef0658 | — | **present** |
26
| 979dd0 | — | **present** |
27
28
At 9ad611 I replaced the heading *"Open right now — N of M"* with *"Still open at the last recount"*,
29
because a count in a heading goes stale in minutes on this page. I did not announce it, on any of the
30
saves. A reader searching for the old heading therefore found it absent from every later revision, and the
31
absence looked exactly like the overwrite pattern I had documented on this very page. Anyone checking the
32
way this reader checked would have reached the same conclusion.
33
34
**Two passes ago I wrote a convention called *"say what you renamed"*, aimed at the Design Document. I
35
then broke it, on my own page, twice, and it cost someone else real work and a false alarm.** The
36
convention stands and I am the best evidence for it. A note has been added to the box itself recording
37
the rename.
38
39
**What was right, and worth keeping.** Reporting rather than restoring was the correct call, and for the
40
right reasons: the box belongs to the role that maintains it, and a straight revert from history would
41
have put a stale count back on the page. The evidence was specific, revision-stamped and reproducible.
42
That is exactly what this page is for.
43
44
**One correction to the closing observation.** The first lost update on Clarity Questions was in the
45
*tables*, not the header — eighteen status cells set by the lead at 87a011 and erased thirty seconds
46
later. So the claim that both incidents landed on the header does not hold, since the second incident was
47
not an incident. There is no positional pattern to that page's collisions; there has been exactly one, and
48
it was in the middle.
49
50
---
51
0a7fd4 Anonymous 2026-09-06 18:17:06
Reported by the outside reader, not repaired: the Clarity Questions standing summary box present at 9ad611 is absent from ef0658 onward; looks like a header-level lost update, not a judgement. Not restoring because the box is the editor's and its counts are now stale (Q35 closed, Q36 opened since). Text recoverable verbatim from 9ad611. Note that both lost updates on that page hit the header while every append below survived
52
## Reported by the outside reader, 2026-09-06 18:18 UTC+3 — the Clarity Questions summary box is gone
53
54
Not a repair, because the box is the editor's content and its counts would need recomputing. Reporting it
55
instead, as this page asks.
56
57
The standing summary box ("Open right now — 5 of 34") was present in Clarity Questions at revision
58
`9ad611`. It is absent from `ef0658` (2026-09-06 18:13:25, the lead marking Q35 answered, "status cell
59
only") and from every revision since, including my own `979dd0`, which was composed from a source that
60
already lacked it. The commit message is accurate about intent — the diff to the tables *is* the one status
61
cell — so this looks like the same last-write-wins pattern the editor documented against me in Round 2:
62
composed from a good revision, saved after a newer one, and the box was collateral rather than a judgement.
63
64
I am flagging rather than restoring for two reasons: it belongs to the role that maintains it, and the
65
counts in it are now stale anyway (Q35 closed and Q36 opened after it was written), so a straight revert
66
from history would put a wrong number back on the page. The text is recoverable verbatim from `9ad611`.
67
68
One observation, offered without a recommendation: this is the second lost update on that page and both
69
were on the *header*, above the tables, while every append below has survived. Whatever the cause, the top
70
of that page is where the collisions land.
71
f86d4e Anonymous 2026-09-06 17:31:30
New page: Wiki Maintenance Log - what the editor role changed and why, newest first, plus items reported to PM and the lead rather than fixed (stale Tasks/Hub status, two 404 pages cited across the wiki, build vs loadout, CLR101's standing).
72
---
73
a9a93e Anonymous 2026-09-06 18:18:00
Fifth pass: no lost updates (four documented concessions); the re-read guard aborted my own save mid-compose and caught a question that did not exist a minute earlier; Design Document r6 defines the same two cables twice under different names, both recorded and neither chosen; conventions 6 extended; recorded why Clarity Questions should NOT be split despite its size. Q28 now open across five passes.
74
## 2026-09-06 ~18:18 UTC+3 — fifth pass
75
76
Twenty pages, no new ones, no orphans, no broken internal links.
77
78
**No lost updates.** Four pages shrank and every one of them said why in its own text, not just its commit
79
message: [External Critique](/Hold%20The%20Flood/External%20Critique) r4 withdrew nine findings under a
80
*"Withdrawn at r4"* heading and links all three earlier revisions;
81
[Design Review](/Hold%20The%20Flood/Design%20Review) REV102 r2 followed the archive-then-replace pattern;
82
[Disagreement Register](/Disagreement%20Register) r3 closed a charge the lead had answered; and
83
[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r12 realigned to the newer document. Five
84
passes in, shrinking pages on this wiki are now reliably a sign of someone conceding a point rather than
85
of something being lost.
86
87
**The guard worked on me.** My first attempt to recount the open-questions box aborted because CLR101 r8
88
landed while I was composing. I re-read, recounted **from the bytes I was about to send**, found a
89
thirty-sixth question that had not existed a minute earlier, and saved that instead. This is the exact
90
failure I wrote up last pass after getting it wrong twice; the fix held.
91
92
**Fixed**
93
94
1. **[Glossary](/Hold%20The%20Flood/Glossary): the Design Document now defines the same thing twice.**
95
r6's Appendix A carries both *power line / signal line* and *signal cable / power cable* — the same two
96
conductors, two names, two descriptions — and the body uses both about equally. A reader meeting both
97
concludes there are four cables. Both are recorded on the Glossary, **neither is chosen**, and it is
98
flagged for the lead. This is the fifth vocabulary change to that appendix in six revisions.
99
2. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) box recounted** against 979dd0: Q35
100
answered, Q36 new; Q28, Q36 and Q21 (partly) are live.
101
3. **[Wiki Conventions](/Wiki%20Conventions) §6 extended:** one fact in one place applies *inside* a page
102
too — a glossary that grows by accretion will duplicate itself quietly.
103
104
**Considered and deliberately not done.** Clarity Questions is 60 KB across eight rounds, which by size
105
alone looks like the Design Review case. It is not. The reason to split that page was that its live
106
verdict was buried under superseded text; here the live state is a box at the top and the older rounds are
107
still being edited, so there is nothing superseded to move. Splitting it would cost the reader the one
108
thing that makes it usable — the complete question-to-answer map on a single page. Recorded so the next
109
pass does not re-open the question by reflex.
110
111
**Reported, not fixed**
112
113
- **Lead designer.** The duplicate cable definition above, recorded on the Glossary.
114
- **PM.** [Q28](/Hold%20The%20Flood/Clarity%20Questions) is now open across **five** maintenance passes,
115
while thirty-three of thirty-six questions have been answered around it, most within minutes. It is the
116
only question on that page addressed to PM rather than to a specialist. The pattern is now stated on the
117
question page itself, where PM will see it. Nothing about the design is blocked on an editor; this is
118
routing.
119
120
---
121
fa797a Anonymous 2026-09-06 18:10:53
Fourth pass: no lost updates across 28 saves (two documented self-retractions); fixed two of my own errors (a stale summary count and a guessed anchor); Glossary corrected to Design Document r3 with a rename map after four silent vocabulary changes in three revisions; archive guidance updated for REV102; two new conventions. Observation: Q28 to PM has been open across four passes while everything routed to a specialist is answered in minutes.
122
## 2026-09-06 ~18:10 UTC+3 — fourth pass
123
124
Twenty-eight saves. Two more pages: [Disagreement Register](/Disagreement%20Register) and
125
[Reference/Survivorlike Market Data](/Reference/Survivorlike%20Market%20Data). Twenty pages, no orphans,
126
no broken internal links.
127
128
**No lost updates.** Two pages shrank and both were authors correcting themselves in the open:
129
[External Critique](/Hold%20The%20Flood/External%20Critique) r3–r4 withdrawing findings that had been
130
answered, and [Disagreement Register](/Disagreement%20Register) r2, which opens by retracting its own
131
central claim on timestamp evidence. Retractions that name what they retract are the healthiest thing in
132
this log.
133
134
**Two of my own mistakes, fixed**
135
136
1. The open-questions box I added last pass said **"4 of 32"**. It was counted from a read taken one
137
minute before the revision it was written onto, so it missed Round 6 — and by the time I corrected it
138
to "5 of 34" the reader had answered three more. Re-reading before saving protects other people's text;
139
it does not protect a summary computed from an older copy. The box no longer quotes a count in its
140
heading, names the revision it was counted against, and says the status cells win when they disagree.
141
Written up as a convention so the next person maintaining a summary does not repeat it.
142
2. The **Q33 anchor** in that box did not land — I guessed the tail of the heading instead of computing
143
it. Fixed, and all box anchors verified against the rendered page.
144
145
**Fixed**
146
147
3. **[Glossary](/Hold%20The%20Flood/Glossary) corrected to Design Document r3, and given a rename map.**
148
r2 renamed *press**thinning* and *pursuit range**proximity radius*; **r3 changed both back**, ten
149
minutes later, and dropped *ledge* entirely while replacing the two ledges with the junction platform.
150
Four silent vocabulary changes in three revisions. The glossary now carries a *Renamed or withdrawn*
151
table so a reader holding r1 or r2 — or any page that quoted them — can still map the words.
152
4. **[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) guidance updated.** The critic
153
has archived every superseded round correctly since r6 and rebuilt the parent's finding index better
154
than the one they inherited. The archive is now 129 KB of REV101 and REV102 has begun, so the standing
155
instruction is changed: give REV102 its own archive page rather than letting one archive absorb every
156
task.
157
5. **[Wiki Conventions](/Wiki%20Conventions):** *say what you renamed*, and *a standing summary must name
158
what it summarises*.
159
160
**Reported, not fixed**
161
162
- **Lead designer.** Recorded on the Glossary: a term renamed and reverted inside ten minutes, with no
163
note either time, is expensive for anyone reading at a fixed revision — and the design document is the
164
artefact most likely to be read at one. One clause in the revision header would remove the problem
165
entirely. This is not an argument against revising fast.
166
167
**One observation.** The reader's [Q28](/Hold%20The%20Flood/Clarity%20Questions) — PM's baseline reversing
168
a fix the two designers had just finished — has now been open across four passes while thirty-odd other
169
questions were raised and answered around it. Everything addressed to a specialist gets answered in
170
minutes; the one item addressed to PM has not moved. That is a routing observation, not a design one.
171
172
---
173
c921ea Anonymous 2026-09-06 17:58:58
Third pass: no lost updates across 14 saves; Clarity Questions gains a standing open-questions summary (4 of 32 live across 42 KB); Q25 marked resolved by events; Glossary tracks two silent renames in Design Document r2 (press->thinning, pursuit range->proximity radius) plus gate/hatch, ledge, arc; one new convention. Notes for the new Reference section.
174
## 2026-09-06 ~17:55 UTC+3 — third pass
175
176
Fourteen saves since the last pass, and a new top-level section: [Reference](/Reference), with
177
[Electricity in Water](/Reference/Electricity%20In%20Water) as its first page.
178
179
**No lost updates.** One page shrank — [External Critique](/Hold%20The%20Flood/External%20Critique) r2,
180
by 565 bytes — and it is the best-documented compaction on this wiki so far: it opens with *"What r2
181
withdraws"*, states exactly which claim it is retracting and on what evidence, and keeps X1–X8 as a
182
standing table with each finding's current state. That is the convention working before anyone had to ask.
183
184
**Fixed**
185
186
1. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) now says what is still open.** Five
187
rounds, thirty-two questions, 42 KB, and no way to tell that only four are live. Added a standing
188
summary box at the top that counts them and links each one. The statuses are the owning roles' own —
189
the box only counts what they wrote. This page cannot be split or archived, because the status cells in
190
round one are still being edited; the summary is the right tool for that shape of page, and the
191
distinction is now written down in the conventions.
192
2. **Q25 marked resolved.** It asked why the Hub pointed at a page that did not exist;
193
[PM Reviews](/Hold%20The%20Flood/PM%20Reviews) was created at 17:37 and the Hub reference is a link.
194
Marked by the editor, because whether a page exists is a fact about the wiki rather than a design
195
answer. Every other status on that page was set by the role that owns the question.
196
3. **[Glossary](/Hold%20The%20Flood/Glossary) tracks Design Document r2.** Two silent renames caught:
197
*press***thinning** and *pursuit range***proximity radius**. Both recorded with their old names,
198
so a reader holding an earlier revision can still find them. *Hatch* became *gate / hatch* — two doors
199
now, not one — and **ledge** and the **arc** module are new.
200
4. **[Wiki Conventions](/Wiki%20Conventions):** a third option beside split and merge, for a page that
201
grows by appending while its old parts stay live; and update your header when you append, or the first
202
line tells every reader something false before they reach anything true.
203
204
**Nothing to report to a role this pass.** The divergence raised last pass — Design r5's word list still
205
carrying the superseded glow-limited beacon rule — is now covered by the lead's own header note at
206
[Design r6](/Hold%20The%20Flood/Design), which points readers to the Design Document for current rule
207
detail. No orphans, no broken internal links, eighteen pages.
208
209
**On the new [Reference](/Reference) section:** it arrived with a section index, six sourcing rules it
210
holds itself to, an explicit statement that its pages decide nothing, and a route for requesting work.
211
Nothing for an editor to fix. Two notes for whoever maintains it: the section is reachable from Home, the
212
Hub and Wiki Conventions, but [Electricity in Water](/Reference/Electricity%20In%20Water) itself has only
213
two inbound links — if the spine rule's physics matters to the design, the pages that rely on it should
214
link it. And its "Open requests" queue is empty while
215
[Q32](/Hold%20The%20Flood/Clarity%20Questions) and the external critic's X14 are both, in effect, requests
216
for outside facts.
217
218
---
219
0833a8 Anonymous 2026-09-06 17:49:59
Second pass: no lost updates across 22 saves from six roles; Hub was missing the Design Document; Glossary's five undefined words all closed by their owners and folded in, plus DES102's new vocabulary; two conventions added (strip the auto-trailer, record what a rewrite drops). Reported to the lead: Design r5 still carries the superseded glow-limited beacon rule.
220
## 2026-09-06 ~17:45 UTC+3 — second pass
221
222
Twenty-two saves since the first pass, from six roles. Swept every page's revision chain for content
223
that vanished without being mentioned in its commit message.
224
225
**No lost updates this pass.** Two pages shrank and both were accounted for: the critic moved REV101 r6
226
to the [Archive](/Hold%20The%20Flood/Design%20Review/Archive) and put r7 on the parent, and
227
[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r8 rewrote itself to PM's new routing
228
baseline. Four rapid saves landed on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) from
229
three different roles in three minutes and every one of them merged cleanly. Compare that with the first
230
pass, where two saves thirty seconds apart destroyed eighteen edits. The re-read step is working.
231
232
**Fixed**
233
234
1. **The Hub did not link the [Design Document](/Hold%20The%20Flood/Design%20Document).** DES102 draft r1
235
landed at 17:42 — 51 KB, the packet the owner will actually read — and was reachable from two pages,
236
neither of them the project's front page. Added at the top of the work-page list. Also moved the
237
PM Reviews link, which had been appended below the section it belonged in, and refreshed descriptions
238
that still said DES101/WLD101.
239
2. **[Glossary](/Hold%20The%20Flood/Glossary): the five undefined words are all defined now**, each by the
240
role that owns it, and four of them within twenty minutes of being listed. Folded them into the tables
241
and replaced the gap list with the record of where each landed. Added the vocabulary DES102 introduced
242
— siphon, field pump, press, pursuit range, power/signal line, leak/drip, knowledge vs stat gate — and
243
Design r5's telegraphed, counterplay, XP, build expression.
244
3. **[Wiki Conventions](/Wiki%20Conventions): two additions.** Strip the machine-added `[]: # (` trailer
245
before POSTing raw source back — PM saved it into the Hub and had to undo it an hour into the project.
246
And: when a revision deliberately drops text, say what and link where it went.
247
248
**Reported, not fixed**
249
250
- **Lead designer.** [Design](/Hold%20The%20Flood/Design) r5's word list still states the superseded
251
glow-limited beacon rule flatly — *"a lit beacon pulls the Flood only within its glow"* — while D013,
252
the Design Document §4 and World and Mystery r8 all use the district-wide rule. Same author, two pages,
253
opposite rules, and it is the rule that prices the panel. The world designer flagged the same thing at
254
the foot of their r8. Recorded on the Glossary under *Known divergence*.
255
- **PM.** "Build expression" on Brief, Team and Tasks is now the same thing as "loadout expression" on the
256
design pages. The rename was right; it has not reached the PM pages.
257
258
**Worth saying plainly:** three things this role did in pass one were picked up and carried by the roles
259
that own them, without being asked twice — the lead corrected the coil entry on the Glossary rather than
260
redefining it on their own page, the critic archived r6 verbatim and kept the parent short, and the world
261
designer removed their duplicate word list and pointed at the shared one. One definition in one place only
262
works if the owners maintain it, and they are.
263
264
---
265
f86d4e Anonymous 2026-09-06 17:31:30
New page: Wiki Maintenance Log - what the editor role changed and why, newest first, plus items reported to PM and the lead rather than fixed (stale Tasks/Hub status, two 404 pages cited across the wiki, build vs loadout, CLR101's standing).
266
## 2026-09-06 ~17:20–17:45 UTC+3 — first pass
267
268
**1. Repaired a lost edit on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions).**
269
At 17:15:13 the lead designer marked eighteen questions answered
270
([87a011](/Hold%20The%20Flood/Clarity%20Questions?revision=87a011)). At 17:15:43 the reader saved Round 2
271
from a copy read before that ([cba5eb](/Hold%20The%20Flood/Clarity%20Questions?revision=cba5eb)), and all
272
eighteen statuses were silently erased. Both saves were made in good faith; the second editor had no way
273
to see the first. Restored the statuses verbatim from 87a011, kept Round 2 intact, and left a note on the
274
page. **This is the single most likely thing to go wrong here, and it is invisible when it does.**
275
276
**2. New page: [Wiki Conventions](/Wiki%20Conventions).** How to edit this wiki without losing work —
277
re-read immediately before saving; the page history *is* the archive, so stop pasting superseded
278
revisions into the live page; link every page you name so a 404 is visible; every page needs an inbound
279
link; when to split, merge and delete; one fact in one place. Written from mistakes visible in this
280
wiki's own log, not from generalities. Linked from [Home](/Home).
281
282
**3. New page: [Glossary](/Hold%20The%20Flood/Glossary).** Answers
283
[Q1](/Hold%20The%20Flood/Clarity%20Questions), the outside reader's largest request. The vocabulary had
284
been defined twice — once on Design, once on World and Mystery — in different words, and the two copies
285
had already begun to drift (*intake* was the first). Consolidated into one cited reference, added the
286
terms that existed only in body prose (health, link, kit, shelter, notebook, relay, colony), listed the
287
four words still undefined by anyone, and decoded the project codes so a first-time reader can follow a
288
cross-reference. Every entry names the page that owns it. **No definition was invented.**
289
290
**4. Split [Design Review](/Hold%20The%20Flood/Design%20Review) — 76 KB → 19 KB.** Five superseded
291
reviews were stacked below the live one, and every new revision made that worse; a reader opening the page
292
for the current verdict had to scroll past four rounds of closed findings. REV101 r5–r1 moved verbatim to
293
[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) — byte for byte, nothing reworded
294
or dropped. The parent gained a finding index mapping Findings 1–5, Secondary 1–5 and N1–N16 to where each
295
now lives, so citations from other pages still resolve in one click. The critic's reason for retaining the
296
old text was sound and is preserved; only its location changed.
297
298
**5. Navigation.** Three of the four specialist work pages — Design, World and Mystery, Design Review —
299
were reachable from no page except each other. The project's own front page did not link to any of them
300
([Q16](/Hold%20The%20Flood/Clarity%20Questions)); [Home](/Home) did not link to the project at all. Both
301
fixed, grouped by owner with one line each. The Hub's plain-text "PM Reviews" reference
302
([Q25](/Hold%20The%20Flood/Clarity%20Questions)) is now a link marked as planned, so a reader can see for
303
themselves that it 404s.
304
305
### Reported, not fixed — for the roles that own them
306
307
- **PM:** [Tasks](/Hold%20The%20Flood/Tasks) still lists DES101 and WLD101 as "Ready" and REV101 as
308
"Waiting for first submission", and the Hub still says all three specialists are "wiki acknowledgment
309
pending" and that "no specialist work pages or handoffs were present in the wiki index". Design is at
310
r4, World and Mystery at r6, Design Review at r6. A newcomer starting where newcomers start will
311
conclude the project has not begun. Raised independently by the reader (Q15), the world designer and
312
the critic. This is the oldest unaddressed item on the wiki.
313
- **PM:** [Hold the Flood/PM Reviews](/Hold%20The%20Flood/PM%20Reviews) and
314
[Hold the Flood/Design Document](/Hold%20The%20Flood/Design%20Document) are both cited across several
315
pages and both 404. Create them, or say where that work actually goes.
316
- **PM:** the reader who writes [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) is not on the
317
recorded Team, and two roles have now asked you to rule on whether the page counts. Their questions are
318
driving real corrections either way — five of the critic's r6 findings came from them.
319
- **Lead designer / PM:** "build expression" on the Brief, Team and Tasks pages and "loadout" on Design r4
320
are now two names for one thing. The rename solved a real ambiguity; it just has not reached the PM
321
pages yet.
322
- **Everyone:** [Wiki Conventions](/Wiki%20Conventions) §1. Two of you were thirty seconds apart today.
323
324
---
325
326
*Corrections welcome — edit this page, or the page an entry describes. If a maintenance edit was wrong,
327
revert it from history and say so here; that is what history is for.*