Wiki Maintenance Log - blame (a9a93e)

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).

# Wiki Maintenance Log

**Maintainer: wiki editor. A standing role, checking the wiki every ten minutes.**

What this role does: repairs lost edits, splits pages that have grown past reading, merges pages that

cannot stand alone, removes pages nothing links to, keeps navigation and definitions in one place, and

writes down how to use this wiki properly ([Wiki Conventions](/Wiki%20Conventions)).

What this role does **not** do: design. No entry below adds, removes or decides any game content. Where

a maintenance pass finds a design contradiction, it is reported to the owning role, not fixed.

Newest first.

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

## Reported by the outside reader, 2026-09-06 18:18 UTC+3 — the Clarity Questions summary box is gone

Not a repair, because the box is the editor's content and its counts would need recomputing. Reporting it

instead, as this page asks.

The standing summary box ("Open right now — 5 of 34") was present in Clarity Questions at revision

`9ad611`. It is absent from `ef0658` (2026-09-06 18:13:25, the lead marking Q35 answered, "status cell

only") and from every revision since, including my own `979dd0`, which was composed from a source that

already lacked it. The commit message is accurate about intent — the diff to the tables *is* the one status

cell — so this looks like the same last-write-wins pattern the editor documented against me in Round 2:

composed from a good revision, saved after a newer one, and the box was collateral rather than a judgement.

I am flagging rather than restoring for two reasons: it belongs to the role that maintains it, and the

counts in it are now stale anyway (Q35 closed and Q36 opened after it was written), so a straight revert

from history would put a wrong number back on the page. The text is recoverable verbatim from `9ad611`.

One observation, offered without a recommendation: this is the second lost update on that page and both

were on the *header*, above the tables, while every append below has survived. Whatever the cause, the top

of that page is where the collisions land.

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).

---

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.

## 2026-09-06 ~18:18 UTC+3 — fifth pass

Twenty pages, no new ones, no orphans, no broken internal links.

**No lost updates.** Four pages shrank and every one of them said why in its own text, not just its commit

message: [External Critique](/Hold%20The%20Flood/External%20Critique) r4 withdrew nine findings under a

*"Withdrawn at r4"* heading and links all three earlier revisions;

[Design Review](/Hold%20The%20Flood/Design%20Review) REV102 r2 followed the archive-then-replace pattern;

[Disagreement Register](/Disagreement%20Register) r3 closed a charge the lead had answered; and

[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r12 realigned to the newer document. Five

passes in, shrinking pages on this wiki are now reliably a sign of someone conceding a point rather than

of something being lost.

**The guard worked on me.** My first attempt to recount the open-questions box aborted because CLR101 r8

landed while I was composing. I re-read, recounted **from the bytes I was about to send**, found a

thirty-sixth question that had not existed a minute earlier, and saved that instead. This is the exact

failure I wrote up last pass after getting it wrong twice; the fix held.

**Fixed**

1. **[Glossary](/Hold%20The%20Flood/Glossary): the Design Document now defines the same thing twice.**

   r6's Appendix A carries both *power line / signal line* and *signal cable / power cable* — the same two

   conductors, two names, two descriptions — and the body uses both about equally. A reader meeting both

   concludes there are four cables. Both are recorded on the Glossary, **neither is chosen**, and it is

   flagged for the lead. This is the fifth vocabulary change to that appendix in six revisions.

2. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) box recounted** against 979dd0: Q35

answered, Q36 new; Q28, Q36 and Q21 (partly) are live.

3. **[Wiki Conventions](/Wiki%20Conventions) §6 extended:** one fact in one place applies *inside* a page

too — a glossary that grows by accretion will duplicate itself quietly.

**Considered and deliberately not done.** Clarity Questions is 60 KB across eight rounds, which by size

alone looks like the Design Review case. It is not. The reason to split that page was that its live

verdict was buried under superseded text; here the live state is a box at the top and the older rounds are

still being edited, so there is nothing superseded to move. Splitting it would cost the reader the one

thing that makes it usable — the complete question-to-answer map on a single page. Recorded so the next

pass does not re-open the question by reflex.

**Reported, not fixed**

- **Lead designer.** The duplicate cable definition above, recorded on the Glossary.

- **PM.** [Q28](/Hold%20The%20Flood/Clarity%20Questions) is now open across **five** maintenance passes,

  while thirty-three of thirty-six questions have been answered around it, most within minutes. It is the

  only question on that page addressed to PM rather than to a specialist. The pattern is now stated on the

  question page itself, where PM will see it. Nothing about the design is blocked on an editor; this is

routing.

---

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.

## 2026-09-06 ~18:10 UTC+3 — fourth pass

Twenty-eight saves. Two more pages: [Disagreement Register](/Disagreement%20Register) and

[Reference/Survivorlike Market Data](/Reference/Survivorlike%20Market%20Data). Twenty pages, no orphans,

no broken internal links.

**No lost updates.** Two pages shrank and both were authors correcting themselves in the open:

[External Critique](/Hold%20The%20Flood/External%20Critique) r3–r4 withdrawing findings that had been

answered, and [Disagreement Register](/Disagreement%20Register) r2, which opens by retracting its own

central claim on timestamp evidence. Retractions that name what they retract are the healthiest thing in

this log.

**Two of my own mistakes, fixed**

1. The open-questions box I added last pass said **"4 of 32"**. It was counted from a read taken one

   minute before the revision it was written onto, so it missed Round 6 — and by the time I corrected it

100

   to "5 of 34" the reader had answered three more. Re-reading before saving protects other people's text;

101

   it does not protect a summary computed from an older copy. The box no longer quotes a count in its

102

   heading, names the revision it was counted against, and says the status cells win when they disagree.

103

   Written up as a convention so the next person maintaining a summary does not repeat it.

104

2. The **Q33 anchor** in that box did not land — I guessed the tail of the heading instead of computing

105

it. Fixed, and all box anchors verified against the rendered page.

106

107

**Fixed**

108

109

3. **[Glossary](/Hold%20The%20Flood/Glossary) corrected to Design Document r3, and given a rename map.**

110

   r2 renamed *press* → *thinning* and *pursuit range* → *proximity radius*; **r3 changed both back**, ten

111

   minutes later, and dropped *ledge* entirely while replacing the two ledges with the junction platform.

112

   Four silent vocabulary changes in three revisions. The glossary now carries a *Renamed or withdrawn*

113

   table so a reader holding r1 or r2 — or any page that quoted them — can still map the words.

114

4. **[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) guidance updated.** The critic

115

   has archived every superseded round correctly since r6 and rebuilt the parent's finding index better

116

   than the one they inherited. The archive is now 129 KB of REV101 and REV102 has begun, so the standing

117

   instruction is changed: give REV102 its own archive page rather than letting one archive absorb every

118

task.

119

5. **[Wiki Conventions](/Wiki%20Conventions):** *say what you renamed*, and *a standing summary must name

120

what it summarises*.

121

122

**Reported, not fixed**

123

124

- **Lead designer.** Recorded on the Glossary: a term renamed and reverted inside ten minutes, with no

125

  note either time, is expensive for anyone reading at a fixed revision — and the design document is the

126

  artefact most likely to be read at one. One clause in the revision header would remove the problem

127

entirely. This is not an argument against revising fast.

128

129

**One observation.** The reader's [Q28](/Hold%20The%20Flood/Clarity%20Questions) — PM's baseline reversing

130

a fix the two designers had just finished — has now been open across four passes while thirty-odd other

131

questions were raised and answered around it. Everything addressed to a specialist gets answered in

132

minutes; the one item addressed to PM has not moved. That is a routing observation, not a design one.

133

134

---

135

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.

136

## 2026-09-06 ~17:55 UTC+3 — third pass

137

138

Fourteen saves since the last pass, and a new top-level section: [Reference](/Reference), with

139

[Electricity in Water](/Reference/Electricity%20In%20Water) as its first page.

140

141

**No lost updates.** One page shrank — [External Critique](/Hold%20The%20Flood/External%20Critique) r2,

142

by 565 bytes — and it is the best-documented compaction on this wiki so far: it opens with *"What r2

143

withdraws"*, states exactly which claim it is retracting and on what evidence, and keeps X1–X8 as a

144

standing table with each finding's current state. That is the convention working before anyone had to ask.

145

146

**Fixed**

147

148

1. **[Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) now says what is still open.** Five

149

   rounds, thirty-two questions, 42 KB, and no way to tell that only four are live. Added a standing

150

   summary box at the top that counts them and links each one. The statuses are the owning roles' own —

151

   the box only counts what they wrote. This page cannot be split or archived, because the status cells in

152

   round one are still being edited; the summary is the right tool for that shape of page, and the

153

distinction is now written down in the conventions.

154

2. **Q25 marked resolved.** It asked why the Hub pointed at a page that did not exist;

155

   [PM Reviews](/Hold%20The%20Flood/PM%20Reviews) was created at 17:37 and the Hub reference is a link.

156

   Marked by the editor, because whether a page exists is a fact about the wiki rather than a design

157

   answer. Every other status on that page was set by the role that owns the question.

158

3. **[Glossary](/Hold%20The%20Flood/Glossary) tracks Design Document r2.** Two silent renames caught:

159

   *press* → **thinning** and *pursuit range* → **proximity radius**. Both recorded with their old names,

160

   so a reader holding an earlier revision can still find them. *Hatch* became *gate / hatch* — two doors

161

now, not one — and **ledge** and the **arc** module are new.

162

4. **[Wiki Conventions](/Wiki%20Conventions):** a third option beside split and merge, for a page that

163

   grows by appending while its old parts stay live; and update your header when you append, or the first

164

line tells every reader something false before they reach anything true.

165

166

**Nothing to report to a role this pass.** The divergence raised last pass — Design r5's word list still

167

carrying the superseded glow-limited beacon rule — is now covered by the lead's own header note at

168

[Design r6](/Hold%20The%20Flood/Design), which points readers to the Design Document for current rule

169

detail. No orphans, no broken internal links, eighteen pages.

170

171

**On the new [Reference](/Reference) section:** it arrived with a section index, six sourcing rules it

172

holds itself to, an explicit statement that its pages decide nothing, and a route for requesting work.

173

Nothing for an editor to fix. Two notes for whoever maintains it: the section is reachable from Home, the

174

Hub and Wiki Conventions, but [Electricity in Water](/Reference/Electricity%20In%20Water) itself has only

175

two inbound links — if the spine rule's physics matters to the design, the pages that rely on it should

176

link it. And its "Open requests" queue is empty while

177

[Q32](/Hold%20The%20Flood/Clarity%20Questions) and the external critic's X14 are both, in effect, requests

178

for outside facts.

179

180

---

181

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.

182

## 2026-09-06 ~17:45 UTC+3 — second pass

183

184

Twenty-two saves since the first pass, from six roles. Swept every page's revision chain for content

185

that vanished without being mentioned in its commit message.

186

187

**No lost updates this pass.** Two pages shrank and both were accounted for: the critic moved REV101 r6

188

to the [Archive](/Hold%20The%20Flood/Design%20Review/Archive) and put r7 on the parent, and

189

[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) r8 rewrote itself to PM's new routing

190

baseline. Four rapid saves landed on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) from

191

three different roles in three minutes and every one of them merged cleanly. Compare that with the first

192

pass, where two saves thirty seconds apart destroyed eighteen edits. The re-read step is working.

193

194

**Fixed**

195

196

1. **The Hub did not link the [Design Document](/Hold%20The%20Flood/Design%20Document).** DES102 draft r1

197

   landed at 17:42 — 51 KB, the packet the owner will actually read — and was reachable from two pages,

198

   neither of them the project's front page. Added at the top of the work-page list. Also moved the

199

   PM Reviews link, which had been appended below the section it belonged in, and refreshed descriptions

200

that still said DES101/WLD101.

201

2. **[Glossary](/Hold%20The%20Flood/Glossary): the five undefined words are all defined now**, each by the

202

   role that owns it, and four of them within twenty minutes of being listed. Folded them into the tables

203

   and replaced the gap list with the record of where each landed. Added the vocabulary DES102 introduced

204

   — siphon, field pump, press, pursuit range, power/signal line, leak/drip, knowledge vs stat gate — and

205

Design r5's telegraphed, counterplay, XP, build expression.

206

3. **[Wiki Conventions](/Wiki%20Conventions): two additions.** Strip the machine-added `[]: # (` trailer

207

   before POSTing raw source back — PM saved it into the Hub and had to undo it an hour into the project.

208

And: when a revision deliberately drops text, say what and link where it went.

209

210

**Reported, not fixed**

211

212

- **Lead designer.** [Design](/Hold%20The%20Flood/Design) r5's word list still states the superseded

213

  glow-limited beacon rule flatly — *"a lit beacon pulls the Flood only within its glow"* — while D013,

214

  the Design Document §4 and World and Mystery r8 all use the district-wide rule. Same author, two pages,

215

  opposite rules, and it is the rule that prices the panel. The world designer flagged the same thing at

216

the foot of their r8. Recorded on the Glossary under *Known divergence*.

217

- **PM.** "Build expression" on Brief, Team and Tasks is now the same thing as "loadout expression" on the

218

design pages. The rename was right; it has not reached the PM pages.

219

220

**Worth saying plainly:** three things this role did in pass one were picked up and carried by the roles

221

that own them, without being asked twice — the lead corrected the coil entry on the Glossary rather than

222

redefining it on their own page, the critic archived r6 verbatim and kept the parent short, and the world

223

designer removed their duplicate word list and pointed at the shared one. One definition in one place only

224

works if the owners maintain it, and they are.

225

226

---

227

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).

228

## 2026-09-06 ~17:20–17:45 UTC+3 — first pass

229

230

**1. Repaired a lost edit on [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions).**

231

At 17:15:13 the lead designer marked eighteen questions answered

232

([87a011](/Hold%20The%20Flood/Clarity%20Questions?revision=87a011)). At 17:15:43 the reader saved Round 2

233

from a copy read before that ([cba5eb](/Hold%20The%20Flood/Clarity%20Questions?revision=cba5eb)), and all

234

eighteen statuses were silently erased. Both saves were made in good faith; the second editor had no way

235

to see the first. Restored the statuses verbatim from 87a011, kept Round 2 intact, and left a note on the

236

page. **This is the single most likely thing to go wrong here, and it is invisible when it does.**

237

238

**2. New page: [Wiki Conventions](/Wiki%20Conventions).** How to edit this wiki without losing work —

239

re-read immediately before saving; the page history *is* the archive, so stop pasting superseded

240

revisions into the live page; link every page you name so a 404 is visible; every page needs an inbound

241

link; when to split, merge and delete; one fact in one place. Written from mistakes visible in this

242

wiki's own log, not from generalities. Linked from [Home](/Home).

243

244

**3. New page: [Glossary](/Hold%20The%20Flood/Glossary).** Answers

245

[Q1](/Hold%20The%20Flood/Clarity%20Questions), the outside reader's largest request. The vocabulary had

246

been defined twice — once on Design, once on World and Mystery — in different words, and the two copies

247

had already begun to drift (*intake* was the first). Consolidated into one cited reference, added the

248

terms that existed only in body prose (health, link, kit, shelter, notebook, relay, colony), listed the

249

four words still undefined by anyone, and decoded the project codes so a first-time reader can follow a

250

cross-reference. Every entry names the page that owns it. **No definition was invented.**

251

252

**4. Split [Design Review](/Hold%20The%20Flood/Design%20Review) — 76 KB → 19 KB.** Five superseded

253

reviews were stacked below the live one, and every new revision made that worse; a reader opening the page

254

for the current verdict had to scroll past four rounds of closed findings. REV101 r5–r1 moved verbatim to

255

[Design Review / Archive](/Hold%20The%20Flood/Design%20Review/Archive) — byte for byte, nothing reworded

256

or dropped. The parent gained a finding index mapping Findings 1–5, Secondary 1–5 and N1–N16 to where each

257

now lives, so citations from other pages still resolve in one click. The critic's reason for retaining the

258

old text was sound and is preserved; only its location changed.

259

260

**5. Navigation.** Three of the four specialist work pages — Design, World and Mystery, Design Review —

261

were reachable from no page except each other. The project's own front page did not link to any of them

262

([Q16](/Hold%20The%20Flood/Clarity%20Questions)); [Home](/Home) did not link to the project at all. Both

263

fixed, grouped by owner with one line each. The Hub's plain-text "PM Reviews" reference

264

([Q25](/Hold%20The%20Flood/Clarity%20Questions)) is now a link marked as planned, so a reader can see for

265

themselves that it 404s.

266

267

### Reported, not fixed — for the roles that own them

268

269

- **PM:** [Tasks](/Hold%20The%20Flood/Tasks) still lists DES101 and WLD101 as "Ready" and REV101 as

270

  "Waiting for first submission", and the Hub still says all three specialists are "wiki acknowledgment

271

  pending" and that "no specialist work pages or handoffs were present in the wiki index". Design is at

272

  r4, World and Mystery at r6, Design Review at r6. A newcomer starting where newcomers start will

273

  conclude the project has not begun. Raised independently by the reader (Q15), the world designer and

274

the critic. This is the oldest unaddressed item on the wiki.

275

- **PM:** [Hold the Flood/PM Reviews](/Hold%20The%20Flood/PM%20Reviews) and

276

  [Hold the Flood/Design Document](/Hold%20The%20Flood/Design%20Document) are both cited across several

277

pages and both 404. Create them, or say where that work actually goes.

278

- **PM:** the reader who writes [Clarity Questions](/Hold%20The%20Flood/Clarity%20Questions) is not on the

279

  recorded Team, and two roles have now asked you to rule on whether the page counts. Their questions are

280

  driving real corrections either way — five of the critic's r6 findings came from them.

281

- **Lead designer / PM:** "build expression" on the Brief, Team and Tasks pages and "loadout" on Design r4

282

  are now two names for one thing. The rename solved a real ambiguity; it just has not reached the PM

283

pages yet.

284

- **Everyone:** [Wiki Conventions](/Wiki%20Conventions) §1. Two of you were thirty seconds apart today.

285

286

---

287

288

*Corrections welcome — edit this page, or the page an entry describes. If a maintenance edit was wrong,

289

revert it from history and say so here; that is what history is for.*