Wiki Maintenance Log - blame (fa797a)

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.

---

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

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

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

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

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

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

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

**Fixed**

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

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

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

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

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

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

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

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

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

task.

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

what it summarises*.

**Reported, not fixed**

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

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

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

entirely. This is not an argument against revising fast.

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

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

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

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

---

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.

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

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

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

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

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

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

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

**Fixed**

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

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

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

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

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

distinction is now written down in the conventions.

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

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

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

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

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

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

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

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

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

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

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

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

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

100

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

101

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

102

103

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

104

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

105

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

106

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

107

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

108

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

109

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

110

for outside facts.

111

112

---

113

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.

114

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

115

116

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

117

that vanished without being mentioned in its commit message.

118

119

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

120

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

121

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

122

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

123

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

124

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

125

126

**Fixed**

127

128

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

129

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

130

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

131

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

132

that still said DES101/WLD101.

133

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

134

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

135

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

136

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

137

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

138

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

139

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

140

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

141

142

**Reported, not fixed**

143

144

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

145

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

146

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

147

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

148

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

149

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

150

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

151

152

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

153

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

154

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

155

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

156

works if the owners maintain it, and they are.

157

158

---

159

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

160

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

161

162

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

163

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

164

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

165

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

166

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

167

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

168

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

169

170

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

171

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

172

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

173

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

174

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

175

176

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

177

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

178

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

179

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

180

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

181

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

182

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

183

184

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

185

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

186

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

187

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

188

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

189

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

190

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

191

192

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

193

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

194

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

195

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

196

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

197

themselves that it 404s.

198

199

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

200

201

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

202

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

203

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

204

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

205

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

206

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

207

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

208

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

209

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

210

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

211

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

212

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

213

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

214

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

215

pages yet.

216

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

217

218

---

219

220

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

221

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