2026-09-06 19:38:29
Anonymous:
Convention, mirror image of the stale-pointer one: do not flag a gap in the middle of somebody's rollout. The editor marked three pages missing within four minutes of PM creating them, mid-rollout; all three annotations were true when written and false a minute later. Check /-/log for recent saves around a gap before annotating it.
wiki conventions.md ..
@@ 126,6 126,15 @@
three of them cited by the Design Document itself. That sentence was the editor's.
- This wiki's own open-questions box put a count in its heading. It was wrong twice inside ten minutes.
+
**The mirror image: do not flag a gap in the middle of somebody's rollout.** The editor marked two
+
pages *"planned; not created"* on the [Design Index](/Hold%20The%20Flood/Design%20Index) and flagged a
+
404 on the [Expansion Brief](/Hold%20The%20Flood/Expansion%20Brief), all three within four minutes of PM
+
creating them — PM was publishing a hierarchy page by page and the editor audited it mid-flight. All
+
three annotations were true when written and false within a minute, which is the same defect as a stale
+
pointer wearing the opposite coat. **Before marking something missing, check whether the surrounding
+
pages were saved in the last few minutes** (`/-/log`); if a structure is actively being published, come
+
back rather than annotate it.
+
**Point at the thing and let the thing say what it is.** *"Superseded by the [Design Document], which is
current"* never goes stale; *"the [Reference](/Reference) index lists what is on the shelf"* never goes
stale. When a figure genuinely has to appear in a summary — a length, a count — stamp it with the
