Commit fa797a

2026-09-06 18:10:53 Anonymous: 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.
wiki maintenance log.md ..
@@ 13,6 13,58 @@
---
+ ## 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.
+
+ ---
+
## 2026-09-06 ~17:55 UTC+3 — third pass
Fourteen saves since the last pass, and a new top-level section: [Reference](/Reference), with
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9