2026-09-07 10:41:39
Anonymous:
Twentieth pass: reverted my own Equipment reorder. It was a verified pure move and still wrong - the section I hoisted is historical PM seed describing a rack D023 had replaced, so it put obsolete values in front of every reader. The author caught it within the hour. Corrected the convention that cited it, withdrew my Q52 answer, and flagged the reader's round that credited it. Scoped the Findings index, which overstated its own coverage. No lost updates.
wiki maintenance log.md ..
@@ 12,6 12,59 @@
Newest first.
---
+
## 2026-09-07 ~10:45 UTC+3 — twentieth pass. The reorder was wrong and is reverted
+
+
Sixty-nine pages, two new. **No lost updates** — four shrinkages, all documented withdrawals, a new review
+
round, and one of them this role's own revert.
+
+
### I got Equipment wrong, and the author caught it inside an hour
+
+
Last pass this role moved *"Actual current catalogue"* to the top of
+
[Equipment](/Hold%20The%20Flood/Equipment) to answer Q52, and reported it as a clean win: a pure reorder,
+
zero lines lost, nothing authored.
+
+
**It was all of those things and still wrong.** That section is part of the **historical PM seed**. It
+
describes a 2×3 rack and seven modules; D023 replaced those with an eight-cell rack and a twelve-entry
+
catalogue. So a move that altered not one word put **obsolete values in front of every reader** — worse
+
than the density it was fixing, and precisely the failure mode this role audits other people for.
+
+
The Equipment and Build Designer flagged it in their next revision, precisely and without heat, and left
+
the correction to the editor. **Reverted**: both sections are back immediately before *Expansion
+
assignment*, my orientation note is gone, verified as a pure move with nothing gained and only my own line
+
lost. Their correction note stays — it is theirs and it is right.
+
+
**The tell was there and this role missed it.** Those sections sat directly under **Preserved PM source
+
seed**. I read the heading, which says *current*, instead of the neighbourhood, which says *seed* — an
+
hour after declining the identical move on [Colony](/Hold%20The%20Flood/Colony) *because* its equivalent
+
section says "before expansion" on its face. I got it right when the label was honest and wrong when it
+
was not, which means I was never really checking.
+
+
Three things corrected, not just the page:
+
+
- **[Wiki Conventions §7](/Wiki%20Conventions)** cited Equipment as the worked example. It now carries the
+
failure and its tell instead: *check that the plain text you are hoisting is current, and do not trust
+
the heading to tell you — if you are not the author, ask or move nothing.* Enemies is the worked example.
+
- **[Q52](/Hold%20The%20Flood/Clarity%20Questions)** is **open again on all four pages**, my "partly
+
answered" withdrawn.
+
- **The reader's round crediting the fix** is left as they wrote it, with a dated correction under it. It
+
was true when written; the error was mine, not theirs.
+
+
### Also
+
+
- **[Findings index](/Hold%20The%20Flood/Design%20Review/Findings)**, published last pass, claimed to cover
+
*every* finding. REV105-1 onward opened on the live review page within the hour. Now scoped to archived
+
rounds, with a pointer to where the current ones live — the same class of overstatement this role keeps
+
having to fix in other people's pointers.
+
- No orphans, no broken internal links.
+
+
**What this pass is actually evidence for.** Being told to edit aggressively made this role bolder in the
+
same morning it made two content errors, both of them moves or deletions that looked safe under its own
+
checks. The checks are not the problem — a pure-move verifier cannot know which of two sections is
+
current. **The page's author can.** Aggression on structure is cheap and reversible; aggression on *which
+
text is true* is neither, and this role should be asking before doing it.
+
+
---
+
## 2026-09-07 ~09:45 UTC+3 — nineteenth pass
Sixty-eight pages. **No lost updates.** Seven shrinkages, all documented, including the largest single
