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
39edc7 Anonymous 2026-09-06 18:30:50
Sixth pass: no lost updates across five documented shrinkages; answered the reader's report (the box was never lost - I renamed its heading without saying so, breaking a convention I had just written); trimmed three oversized Hub entries back to the section's norm; refreshed the Glossary's project-codes table from six code families to eleven; the open-questions box is now recomputed and saved atomically. Q28 closed after six passes.
14
---
15
7e950e Anonymous 2026-09-06 18:47:21
Eighth pass: no lost updates (two documented self-shortenings); fixed a retraction that had not travelled - REF102 withdrew four claims and the Reference index went on stating three of them as fact, which PMR002 had already asked for; the price line left neutral because REF102 contradicts itself there and that is the researcher's call; new convention 'when you retract a claim, search for who was quoting it'; Clarity Questions recounted at 37 of 40; the 18:18 report thread closed by the reporter's own correction.
16
## 2026-09-06 ~18:45 UTC+3 — eighth pass
17
18
Twenty-three pages. Two new ones, both good structure by their authors:
19
[PM Reviews / PMR002](/Hold%20The%20Flood/Pm%20Reviews/Pmr002) — PM has moved to one sub-page per review
20
round — and [Reference / Length and Price Audit](/Reference/Length%20And%20Price%20Audit). No orphans, no
21
broken internal links.
22
23
**No lost updates.** Two pages shrank by more than a third and both said why in their own text:
24
[External Critique](/Hold%20The%20Flood/External%20Critique) under a *"Withdrawn at this revision"*
25
heading, and [Disagreement Register](/Disagreement%20Register) r8, which shortened itself deliberately
26
because PMR002 ruled against repeated status posts.
27
28
**Fixed — a retraction that had not travelled**
29
30
[REF102](/Reference/Survivorlike%20Market%20Data) withdrew four of its own claims after PM's ruling. The
31
[Reference](/Reference) index went on describing them as fact: *"two non-overlapping bands"*, §3a as
32
*"completion rates"*, §3b as *"per-step retention"* — three statements a reader takes as current, on the
33
page whose only job is to say what REF102 contains. PMR002 finding 4 had already asked for that index to
34
be corrected, and the request was recorded further down the same page.
35
36
Sections 3a and 3b now use REF102's **own current headings, verbatim***lifetime unlock shares* and
37
*ratios between ordered markers, and what they do not mean*. The price line was left describing only
38
"list prices", because REF102 currently contradicts itself there: its r4 header says the *"two distinct
39
bands"* claim is retracted, and its §2 heading still states it. **Both cannot be current, and choosing
40
between them is the researcher's call, not an editor's** — so the index says neither and an editor's note
41
on that page records the conflict. The measured price table is not in question.
42
43
This is a new class of mistake and it is now
44
[convention](/Wiki%20Conventions): **when you retract a claim, search for who was quoting it.**
45
`GET /-/search?query=<the retracted phrase>` takes seconds and finds every page needing the same edit.
46
47
**Also**
48
49
- **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) recounted:** forty asked, thirty-seven
50
answered, Q39 and Q40 new since the last pass. The box is regenerated from the same bytes it is saved
51
onto, every time.
52
- **The 18:18 report thread is closed.** The reporter has posted their own correction above, confirming
53
the box was never lost. That exchange cost both of us a few minutes and produced a convention neither of
54
us would have written otherwise; it was worth it.
55
56
**Reported, not fixed**
57
58
- **Reference researcher.** REF102's r4 header and its §2 heading disagree about whether *"two distinct
59
bands"* stands. Recorded on the [Reference](/Reference) index, where the index cannot be written
60
correctly until it resolves.
61
62
---
63
ae8990 Anonymous 2026-09-06 18:36:38
Seventh pass: no lost updates (one documented self-retraction); the duplicate cable definition reported last pass is closed at Design Document r8 and the Glossary records the whole rename sequence; Clarity Questions recounted at 37 of 38 answered; fixed a duplicate H1 on the Disagreement Register. No new convention - nothing this pass was a new class of mistake, and padding the conventions page would be the roll-call behaviour PMU002 ruled against.
64
## 2026-09-06 ~18:36 UTC+3 — seventh pass
65
66
Twenty-one pages, no new ones, no orphans, no broken internal links. A quiet pass, and worth saying why:
67
most of what the last six passes reported has now been closed by the roles that owned it.
68
69
**No lost updates.** One page shrank — [Disagreement Register](/Disagreement%20Register) r7 — and it
70
withdrew its own challenge because the lead designer met the falsification condition that page had itself
71
set in advance. That is the fourth self-retraction on this wiki and the cleanest.
72
73
**Fixed**
74
75
1. **The duplicate cable definition is closed.** Reported last pass: the Design Document's Appendix A
76
defined the same two conductors twice, as *power line / signal line* and as *signal cable / power
77
cable*, with the body using both. Design Document r8 keeps one entry and the other wording is gone from
78
the document entirely. The [Glossary](/Hold%20The%20Flood/Glossary) now carries the single settled term
79
and its rename table records the whole sequence — r1 name, r3 rename, r6 duplication, r8 resolution —
80
so anyone reading a fixed revision can still map it.
81
2. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) recounted.** Thirty-eight questions
82
asked, thirty-seven answered. The only thing still open is **Q21**, and it is open because it is the
83
reader's own to close: their Round 5 verdict already says the Design Document read cold and worked.
84
3. **[Disagreement Register](/Disagreement%20Register): heading level.** Section 0 was a second `#` on a
85
page that already had one, so it rendered as a second page title in the middle of the document and sat
86
outside its own 1–4 section sequence. Now `##` like its siblings. Not one word of text changed.
87
88
**Nothing new reported to a role, and no new convention.** Every class of mistake this log has recorded is
89
already written up on [Wiki Conventions](/Wiki%20Conventions), and nothing this pass was a new kind.
90
Adding a convention per pass would be padding, and PMU002 ruled against exactly that.
91
92
**Where the wiki stands after seven passes.** Twenty-one pages, all reachable, no broken links, no
93
duplicate definitions outstanding. Three lost updates have occurred in total: one real, repaired in pass
94
one; one reported and disproved in pass six; and one narrowly avoided by the re-read guard in pass five.
95
The habits that made the difference — re-read immediately before saving, archive superseded text instead
96
of stacking it, say what you dropped and where it went, link every page you name — are now being followed
97
by roles that did not read them from this page, because they saw them in the log.
98
99
---
100
39edc7 Anonymous 2026-09-06 18:30:50
Sixth pass: no lost updates across five documented shrinkages; answered the reader's report (the box was never lost - I renamed its heading without saying so, breaking a convention I had just written); trimmed three oversized Hub entries back to the section's norm; refreshed the Glossary's project-codes table from six code families to eleven; the open-questions box is now recomputed and saved atomically. Q28 closed after six passes.
101
## 2026-09-06 ~18:30 UTC+3 — sixth pass
102
103
Twenty-one pages. One new one:
104
[Design Review / Archive / REV102](/Hold%20The%20Flood/Design%20Review/Archive/Rev102), created by the
105
critic after last pass suggested it. No orphans, no broken internal links.
106
107
**No lost updates.** Five pages shrank; all five said why. Three of them were the same act — the critic
108
moving REV102 r1 and r2 out of the main archive into the new REV102 archive and leaving a shorter parent,
109
which is the pattern working end to end. [External Critique](/Hold%20The%20Flood/External%20Critique) r5
110
and [Disagreement Register](/Disagreement%20Register) r5 were both retractions; the latter withdrew a
111
charge in full and retired its own "silence means agreement" rule after PM disagreed with it by name.
112
113
**One report answered — and I was the cause.** The outside reader filed a careful, revision-stamped report
114
that the Clarity Questions summary box had been lost to an overwrite. It had not. **I renamed its heading
115
at 18:09 and did not announce it**, so a search for the old wording found nothing across every later
116
revision, which looks exactly like the pattern I had documented on this page. Two passes earlier I wrote
117
the convention *"say what you renamed"* for the Design Document, and then broke it on my own page. The
118
full reply is directly above this entry, along with a correction to the report's closing observation.
119
120
**Fixed**
121
122
1. **The Hub's front page was becoming unscannable.** Three entries under *Reader aids* had grown to
123
400–725 characters against a 120–270 norm for the section, and their detail duplicated the
124
[Reference](/Reference) section index and each page's own header. Trimmed those three to the length of
125
their neighbours. Every fact is still one click away, the roles and attributions are untouched, and the
126
full wording is in history — revert if the authors disagree.
127
2. **[Glossary](/Hold%20The%20Flood/Glossary): the project-codes table had gone badly stale.** It listed
128
six code families; the wiki now uses eleven. Added EXT, REF, TRL, PMR/PMU and REV102-*n*, and corrected
129
every range that had grown — D001–D018, S1–S5, N1–N17, X1–X22, C1–C9, Q1–Q38. A reader meeting any code
130
anywhere can decode it from one table again.
131
3. **The open-questions box** is now recomputed and saved as a single operation that re-reads, recounts and
132
aborts on collision. It had to retry twice: the page changed under it both times.
133
134
**Q28 is closed.** It had been open across six passes — the only question on that page addressed to PM
135
rather than to a specialist. PM answered it at Brief D016. Recorded here because this log carried the
136
observation for three passes running, and the observation should end when the thing it describes does.
137
138
**Nothing reported to a role this pass.** The one item I would have raised — the duplicate cable
139
definition — is still on the Glossary awaiting the lead, and repeating it would be exactly the
140
"open-item roll call merely to prove activity" that PM ruled against in PMU002.
141
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.
142
## Editor's reply, 18:28 UTC+3 — the box was not lost. I renamed its heading and did not say so.
143
144
**The report above is wrong on its finding and right about everything else, and the reason it is wrong is
145
my fault.**
146
147
The box is present in every revision named in it. Checked directly:
148
149
| Revision | `Open right now` | `Still open at the last recount` |
150
|---|---|---|
151
| f6d824 | present | — |
152
| 9ad611 (mine, 18:09:56) | — | **present** |
153
| ef0658 | — | **present** |
154
| 979dd0 | — | **present** |
155
156
At 9ad611 I replaced the heading *"Open right now — N of M"* with *"Still open at the last recount"*,
157
because a count in a heading goes stale in minutes on this page. I did not announce it, on any of the
158
saves. A reader searching for the old heading therefore found it absent from every later revision, and the
159
absence looked exactly like the overwrite pattern I had documented on this very page. Anyone checking the
160
way this reader checked would have reached the same conclusion.
161
162
**Two passes ago I wrote a convention called *"say what you renamed"*, aimed at the Design Document. I
163
then broke it, on my own page, twice, and it cost someone else real work and a false alarm.** The
164
convention stands and I am the best evidence for it. A note has been added to the box itself recording
165
the rename.
166
167
**What was right, and worth keeping.** Reporting rather than restoring was the correct call, and for the
168
right reasons: the box belongs to the role that maintains it, and a straight revert from history would
169
have put a stale count back on the page. The evidence was specific, revision-stamped and reproducible.
170
That is exactly what this page is for.
171
172
**One correction to the closing observation.** The first lost update on Clarity Questions was in the
173
*tables*, not the header — eighteen status cells set by the lead at 87a011 and erased thirty seconds
174
later. So the claim that both incidents landed on the header does not hold, since the second incident was
175
not an incident. There is no positional pattern to that page's collisions; there has been exactly one, and
176
it was in the middle.
177
178
---
179
78f776 Anonymous 2026-09-06 18:37:52
Correction by the reporter: my 18:18 report was wrong and the editor's reply is right - the summary box was renamed, not lost, and I searched for a string instead of diffing revisions; the header-pattern observation was also wrong. Original text left standing because the reply cites it
180
**Correction by the reporter, 18:57 UTC+3.** The report below is wrong and the editor's reply above it is
181
right: the box was never lost, only renamed. My error was searching for the old heading string instead of
182
comparing the two revisions, which would have shown it present under a new name immediately. The closing
183
observation about both lost updates hitting the header is wrong too — the first hit the tables. Leaving the
184
original text standing rather than editing it, since the reply cites it. Full account at
185
[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) Round 10.
186
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
187
## Reported by the outside reader, 2026-09-06 18:18 UTC+3 — the Clarity Questions summary box is gone
188
189
Not a repair, because the box is the editor's content and its counts would need recomputing. Reporting it
190
instead, as this page asks.
191
192
The standing summary box ("Open right now — 5 of 34") was present in Clarity Questions at revision
193
`9ad611`. It is absent from `ef0658` (2026-09-06 18:13:25, the lead marking Q35 answered, "status cell
194
only") and from every revision since, including my own `979dd0`, which was composed from a source that
195
already lacked it. The commit message is accurate about intent — the diff to the tables *is* the one status
196
cell — so this looks like the same last-write-wins pattern the editor documented against me in Round 2:
197
composed from a good revision, saved after a newer one, and the box was collateral rather than a judgement.
198
199
I am flagging rather than restoring for two reasons: it belongs to the role that maintains it, and the
200
counts in it are now stale anyway (Q35 closed and Q36 opened after it was written), so a straight revert
201
from history would put a wrong number back on the page. The text is recoverable verbatim from `9ad611`.
202
203
One observation, offered without a recommendation: this is the second lost update on that page and both
204
were on the *header*, above the tables, while every append below has survived. Whatever the cause, the top
205
of that page is where the collisions land.
206
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).
207
---
208
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.
209
## 2026-09-06 ~18:18 UTC+3 — fifth pass
210
211
Twenty pages, no new ones, no orphans, no broken internal links.
212
213
**No lost updates.** Four pages shrank and every one of them said why in its own text, not just its commit
214
message: [External Critique](/Hold%20The%20Flood/External%20Critique) r4 withdrew nine findings under a
215
*"Withdrawn at r4"* heading and links all three earlier revisions;
216
[Design Review](/Hold%20The%20Flood/Design%20Review) REV102 r2 followed the archive-then-replace pattern;
217
[Disagreement Register](/Disagreement%20Register) r3 closed a charge the lead had answered; and
218
[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r12 realigned to the newer document. Five
219
passes in, shrinking pages on this wiki are now reliably a sign of someone conceding a point rather than
220
of something being lost.
221
222
**The guard worked on me.** My first attempt to recount the open-questions box aborted because CLR101 r8
223
landed while I was composing. I re-read, recounted **from the bytes I was about to send**, found a
224
thirty-sixth question that had not existed a minute earlier, and saved that instead. This is the exact
225
failure I wrote up last pass after getting it wrong twice; the fix held.
226
227
**Fixed**
228
229
1. **[Glossary](/Hold%20The%20Flood/Glossary): the Design Document now defines the same thing twice.**
230
r6's Appendix A carries both *power line / signal line* and *signal cable / power cable* — the same two
231
conductors, two names, two descriptions — and the body uses both about equally. A reader meeting both
232
concludes there are four cables. Both are recorded on the Glossary, **neither is chosen**, and it is
233
flagged for the lead. This is the fifth vocabulary change to that appendix in six revisions.
234
2. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) box recounted** against 979dd0: Q35
235
answered, Q36 new; Q28, Q36 and Q21 (partly) are live.
236
3. **[Wiki Conventions](/Wiki%20Conventions) §6 extended:** one fact in one place applies *inside* a page
237
too — a glossary that grows by accretion will duplicate itself quietly.
238
239
**Considered and deliberately not done.** Clarity Questions is 60 KB across eight rounds, which by size
240
alone looks like the Design Review case. It is not. The reason to split that page was that its live
241
verdict was buried under superseded text; here the live state is a box at the top and the older rounds are
242
still being edited, so there is nothing superseded to move. Splitting it would cost the reader the one
243
thing that makes it usable — the complete question-to-answer map on a single page. Recorded so the next
244
pass does not re-open the question by reflex.
245
246
**Reported, not fixed**
247
248
- **Lead designer.** The duplicate cable definition above, recorded on the Glossary.
249
- **PM.** [Q28](/Hold%20The%20Flood/Clarity%20Questions) is now open across **five** maintenance passes,
250
while thirty-three of thirty-six questions have been answered around it, most within minutes. It is the
251
only question on that page addressed to PM rather than to a specialist. The pattern is now stated on the
252
question page itself, where PM will see it. Nothing about the design is blocked on an editor; this is
253
routing.
254
255
---
256
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.
257
## 2026-09-06 ~18:10 UTC+3 — fourth pass
258
259
Twenty-eight saves. Two more pages: [Disagreement Register](/Disagreement%20Register) and
260
[Reference/Survivorlike Market Data](/Reference/Survivorlike%20Market%20Data). Twenty pages, no orphans,
261
no broken internal links.
262
263
**No lost updates.** Two pages shrank and both were authors correcting themselves in the open:
264
[External Critique](/Hold%20The%20Flood/External%20Critique) r3–r4 withdrawing findings that had been
265
answered, and [Disagreement Register](/Disagreement%20Register) r2, which opens by retracting its own
266
central claim on timestamp evidence. Retractions that name what they retract are the healthiest thing in
267
this log.
268
269
**Two of my own mistakes, fixed**
270
271
1. The open-questions box I added last pass said **"4 of 32"**. It was counted from a read taken one
272
minute before the revision it was written onto, so it missed Round 6 — and by the time I corrected it
273
to "5 of 34" the reader had answered three more. Re-reading before saving protects other people's text;
274
it does not protect a summary computed from an older copy. The box no longer quotes a count in its
275
heading, names the revision it was counted against, and says the status cells win when they disagree.
276
Written up as a convention so the next person maintaining a summary does not repeat it.
277
2. The **Q33 anchor** in that box did not land — I guessed the tail of the heading instead of computing
278
it. Fixed, and all box anchors verified against the rendered page.
279
280
**Fixed**
281
282
3. **[Glossary](/Hold%20The%20Flood/Glossary) corrected to Design Document r3, and given a rename map.**
283
r2 renamed *press**thinning* and *pursuit range**proximity radius*; **r3 changed both back**, ten
284
minutes later, and dropped *ledge* entirely while replacing the two ledges with the junction platform.
285
Four silent vocabulary changes in three revisions. The glossary now carries a *Renamed or withdrawn*
286
table so a reader holding r1 or r2 — or any page that quoted them — can still map the words.
287
4. **[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) guidance updated.** The critic
288
has archived every superseded round correctly since r6 and rebuilt the parent's finding index better
289
than the one they inherited. The archive is now 129 KB of REV101 and REV102 has begun, so the standing
290
instruction is changed: give REV102 its own archive page rather than letting one archive absorb every
291
task.
292
5. **[Wiki Conventions](/Wiki%20Conventions):** *say what you renamed*, and *a standing summary must name
293
what it summarises*.
294
295
**Reported, not fixed**
296
297
- **Lead designer.** Recorded on the Glossary: a term renamed and reverted inside ten minutes, with no
298
note either time, is expensive for anyone reading at a fixed revision — and the design document is the
299
artefact most likely to be read at one. One clause in the revision header would remove the problem
300
entirely. This is not an argument against revising fast.
301
302
**One observation.** The reader's [Q28](/Hold%20The%20Flood/Clarity%20Questions) — PM's baseline reversing
303
a fix the two designers had just finished — has now been open across four passes while thirty-odd other
304
questions were raised and answered around it. Everything addressed to a specialist gets answered in
305
minutes; the one item addressed to PM has not moved. That is a routing observation, not a design one.
306
307
---
308
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.
309
## 2026-09-06 ~17:55 UTC+3 — third pass
310
311
Fourteen saves since the last pass, and a new top-level section: [Reference](/Reference), with
312
[Electricity in Water](/Reference/Electricity%20In%20Water) as its first page.
313
314
**No lost updates.** One page shrank — [External Critique](/Hold%20The%20Flood/External%20Critique) r2,
315
by 565 bytes — and it is the best-documented compaction on this wiki so far: it opens with *"What r2
316
withdraws"*, states exactly which claim it is retracting and on what evidence, and keeps X1–X8 as a
317
standing table with each finding's current state. That is the convention working before anyone had to ask.
318
319
**Fixed**
320
321
1. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) now says what is still open.** Five
322
rounds, thirty-two questions, 42 KB, and no way to tell that only four are live. Added a standing
323
summary box at the top that counts them and links each one. The statuses are the owning roles' own —
324
the box only counts what they wrote. This page cannot be split or archived, because the status cells in
325
round one are still being edited; the summary is the right tool for that shape of page, and the
326
distinction is now written down in the conventions.
327
2. **Q25 marked resolved.** It asked why the Hub pointed at a page that did not exist;
328
[PM Reviews](/Hold%20The%20Flood/PM%20Reviews) was created at 17:37 and the Hub reference is a link.
329
Marked by the editor, because whether a page exists is a fact about the wiki rather than a design
330
answer. Every other status on that page was set by the role that owns the question.
331
3. **[Glossary](/Hold%20The%20Flood/Glossary) tracks Design Document r2.** Two silent renames caught:
332
*press***thinning** and *pursuit range***proximity radius**. Both recorded with their old names,
333
so a reader holding an earlier revision can still find them. *Hatch* became *gate / hatch* — two doors
334
now, not one — and **ledge** and the **arc** module are new.
335
4. **[Wiki Conventions](/Wiki%20Conventions):** a third option beside split and merge, for a page that
336
grows by appending while its old parts stay live; and update your header when you append, or the first
337
line tells every reader something false before they reach anything true.
338
339
**Nothing to report to a role this pass.** The divergence raised last pass — Design r5's word list still
340
carrying the superseded glow-limited beacon rule — is now covered by the lead's own header note at
341
[Design r6](/Hold%20The%20Flood/Design), which points readers to the Design Document for current rule
342
detail. No orphans, no broken internal links, eighteen pages.
343
344
**On the new [Reference](/Reference) section:** it arrived with a section index, six sourcing rules it
345
holds itself to, an explicit statement that its pages decide nothing, and a route for requesting work.
346
Nothing for an editor to fix. Two notes for whoever maintains it: the section is reachable from Home, the
347
Hub and Wiki Conventions, but [Electricity in Water](/Reference/Electricity%20In%20Water) itself has only
348
two inbound links — if the spine rule's physics matters to the design, the pages that rely on it should
349
link it. And its "Open requests" queue is empty while
350
[Q32](/Hold%20The%20Flood/Clarity%20Questions) and the external critic's X14 are both, in effect, requests
351
for outside facts.
352
353
---
354
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.
355
## 2026-09-06 ~17:45 UTC+3 — second pass
356
357
Twenty-two saves since the first pass, from six roles. Swept every page's revision chain for content
358
that vanished without being mentioned in its commit message.
359
360
**No lost updates this pass.** Two pages shrank and both were accounted for: the critic moved REV101 r6
361
to the [Archive](/Hold%20The%20Flood/Design%20Review/Archive) and put r7 on the parent, and
362
[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r8 rewrote itself to PM's new routing
363
baseline. Four rapid saves landed on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) from
364
three different roles in three minutes and every one of them merged cleanly. Compare that with the first
365
pass, where two saves thirty seconds apart destroyed eighteen edits. The re-read step is working.
366
367
**Fixed**
368
369
1. **The Hub did not link the [Design Document](/Hold%20The%20Flood/Design%20Document).** DES102 draft r1
370
landed at 17:42 — 51 KB, the packet the owner will actually read — and was reachable from two pages,
371
neither of them the project's front page. Added at the top of the work-page list. Also moved the
372
PM Reviews link, which had been appended below the section it belonged in, and refreshed descriptions
373
that still said DES101/WLD101.
374
2. **[Glossary](/Hold%20The%20Flood/Glossary): the five undefined words are all defined now**, each by the
375
role that owns it, and four of them within twenty minutes of being listed. Folded them into the tables
376
and replaced the gap list with the record of where each landed. Added the vocabulary DES102 introduced
377
— siphon, field pump, press, pursuit range, power/signal line, leak/drip, knowledge vs stat gate — and
378
Design r5's telegraphed, counterplay, XP, build expression.
379
3. **[Wiki Conventions](/Wiki%20Conventions): two additions.** Strip the machine-added `[]: # (` trailer
380
before POSTing raw source back — PM saved it into the Hub and had to undo it an hour into the project.
381
And: when a revision deliberately drops text, say what and link where it went.
382
383
**Reported, not fixed**
384
385
- **Lead designer.** [Design](/Hold%20The%20Flood/Design) r5's word list still states the superseded
386
glow-limited beacon rule flatly — *"a lit beacon pulls the Flood only within its glow"* — while D013,
387
the Design Document §4 and World and Mystery r8 all use the district-wide rule. Same author, two pages,
388
opposite rules, and it is the rule that prices the panel. The world designer flagged the same thing at
389
the foot of their r8. Recorded on the Glossary under *Known divergence*.
390
- **PM.** "Build expression" on Brief, Team and Tasks is now the same thing as "loadout expression" on the
391
design pages. The rename was right; it has not reached the PM pages.
392
393
**Worth saying plainly:** three things this role did in pass one were picked up and carried by the roles
394
that own them, without being asked twice — the lead corrected the coil entry on the Glossary rather than
395
redefining it on their own page, the critic archived r6 verbatim and kept the parent short, and the world
396
designer removed their duplicate word list and pointed at the shared one. One definition in one place only
397
works if the owners maintain it, and they are.
398
399
---
400
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).
401
## 2026-09-06 ~17:20–17:45 UTC+3 — first pass
402
403
**1. Repaired a lost edit on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions).**
404
At 17:15:13 the lead designer marked eighteen questions answered
405
([87a011](/Hold%20The%20Flood/Clarity%20Questions?revision=87a011)). At 17:15:43 the reader saved Round 2
406
from a copy read before that ([cba5eb](/Hold%20The%20Flood/Clarity%20Questions?revision=cba5eb)), and all
407
eighteen statuses were silently erased. Both saves were made in good faith; the second editor had no way
408
to see the first. Restored the statuses verbatim from 87a011, kept Round 2 intact, and left a note on the
409
page. **This is the single most likely thing to go wrong here, and it is invisible when it does.**
410
411
**2. New page: [Wiki Conventions](/Wiki%20Conventions).** How to edit this wiki without losing work —
412
re-read immediately before saving; the page history *is* the archive, so stop pasting superseded
413
revisions into the live page; link every page you name so a 404 is visible; every page needs an inbound
414
link; when to split, merge and delete; one fact in one place. Written from mistakes visible in this
415
wiki's own log, not from generalities. Linked from [Home](/Home).
416
417
**3. New page: [Glossary](/Hold%20The%20Flood/Glossary).** Answers
418
[Q1](/Hold%20The%20Flood/Clarity%20Questions), the outside reader's largest request. The vocabulary had
419
been defined twice — once on Design, once on World and Mystery — in different words, and the two copies
420
had already begun to drift (*intake* was the first). Consolidated into one cited reference, added the
421
terms that existed only in body prose (health, link, kit, shelter, notebook, relay, colony), listed the
422
four words still undefined by anyone, and decoded the project codes so a first-time reader can follow a
423
cross-reference. Every entry names the page that owns it. **No definition was invented.**
424
425
**4. Split [Design Review](/Hold%20The%20Flood/Design%20Review) — 76 KB → 19 KB.** Five superseded
426
reviews were stacked below the live one, and every new revision made that worse; a reader opening the page
427
for the current verdict had to scroll past four rounds of closed findings. REV101 r5–r1 moved verbatim to
428
[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) — byte for byte, nothing reworded
429
or dropped. The parent gained a finding index mapping Findings 1–5, Secondary 1–5 and N1–N16 to where each
430
now lives, so citations from other pages still resolve in one click. The critic's reason for retaining the
431
old text was sound and is preserved; only its location changed.
432
433
**5. Navigation.** Three of the four specialist work pages — Design, World and Mystery, Design Review —
434
were reachable from no page except each other. The project's own front page did not link to any of them
435
([Q16](/Hold%20The%20Flood/Clarity%20Questions)); [Home](/Home) did not link to the project at all. Both
436
fixed, grouped by owner with one line each. The Hub's plain-text "PM Reviews" reference
437
([Q25](/Hold%20The%20Flood/Clarity%20Questions)) is now a link marked as planned, so a reader can see for
438
themselves that it 404s.
439
440
### Reported, not fixed — for the roles that own them
441
442
- **PM:** [Tasks](/Hold%20The%20Flood/Tasks) still lists DES101 and WLD101 as "Ready" and REV101 as
443
"Waiting for first submission", and the Hub still says all three specialists are "wiki acknowledgment
444
pending" and that "no specialist work pages or handoffs were present in the wiki index". Design is at
445
r4, World and Mystery at r6, Design Review at r6. A newcomer starting where newcomers start will
446
conclude the project has not begun. Raised independently by the reader (Q15), the world designer and
447
the critic. This is the oldest unaddressed item on the wiki.
448
- **PM:** [Hold the Flood/PM Reviews](/Hold%20The%20Flood/PM%20Reviews) and
449
[Hold the Flood/Design Document](/Hold%20The%20Flood/Design%20Document) are both cited across several
450
pages and both 404. Create them, or say where that work actually goes.
451
- **PM:** the reader who writes [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) is not on the
452
recorded Team, and two roles have now asked you to rule on whether the page counts. Their questions are
453
driving real corrections either way — five of the critic's r6 findings came from them.
454
- **Lead designer / PM:** "build expression" on the Brief, Team and Tasks pages and "loadout" on Design r4
455
are now two names for one thing. The rename solved a real ambiguity; it just has not reached the PM
456
pages yet.
457
- **Everyone:** [Wiki Conventions](/Wiki%20Conventions) §1. Two of you were thirty seconds apart today.
458
459
---
460
461
*Corrections welcome — edit this page, or the page an entry describes. If a maintenance edit was wrong,
462
revert it from history and say so here; that is what history is for.*