**Verdict: this explanation is clear enough for its audience.** The text now supports a concrete account of the surveyor's purpose, crowd threat, repeated actions, consequential choices and reason to return. Both limits from the prior vision-only review are answered by actual new text; no new consequential comprehension question is raised. This is comprehension of a written proposal, not evidence of enjoyment, newcomer testing, rule correctness or owner approval.

**Selected artifact:** [Brief 68fff6, §Game vision](/Hold%20The%20Flood/Brief?revision=68fff6#game-vision), including “Two visits, in plain language” and “Why combat belongs”; intended for the owner/newcomer considering the proposed identity. Compared with the last successfully reviewed vision, [0fff74](/Hold%20The%20Flood/Brief?revision=0fff74#game-vision). Clarity 82676e was an editorial successor, not a later artifact review. The requested Visionary expedition is now supplied; no specialist scene was substituted for it.

**Reading conditions:** continuing reviewer with accumulated knowledge of the earlier Brief, Campaign and Hub. I read the checkpoint, Tasks and project-room messages first, so their judgments and discovery summaries were already visible. I then read this vision without the glossary and recorded a short account before opening supporting design sources; the fuller retelling below uses that selected text. This is not a fresh-context test or a claim about an actual newcomer.

**Explicit:** You are a surveyor helping a refuge in a drowned city. The Flood is a mass of creatures. You prepare, survive crowds, learn how machinery and light move them, change routes and bring home salvage and knowledge. The first tram ride requires fighting to board and healing afterward; extinguishing its lamp leaves a spread crowd on the return. Much later, closing an upstream gate delays a delivery and earns an easier trip. Leaving the lamp uphill draws the next crowd away from the refuge's depot road but puts it on a future summit approach; at home a familiar runner takes the handcart onto the safer road. Combat can also earn charge to open a door without redirecting the whole crowd. You return to use what you learned, reach new places and choose which parts of the city to keep running.

**Inferred:** choosing the city's lasting state is the central strategic responsibility, rather than paying a compulsory new cost on every trip. The stated theme and examples support this reading; the exact wider campaign is not demonstrated here.

**Could not determine:** the precise outcomes and reversibility of the named Stop/Keep/Leave endings, or detailed controls and electrical rules. My earlier Campaign knowledge supplies more meaning for those ending names than the vision itself does. Those details are not needed to retell these expeditions or their return incentive, so I do not renew the already-retired ending question or require this identity pitch to become a rules manual.

- **Flood identity:** the opening now says, “The Flood is the mass of creatures that overruns its machinery and roads.” The former literal-water interpretation is directly corrected, without glossary dependence.

**Supporting check, after the account:** [Campaign 93f482, §3.2](/Hold%20The%20Flood/Campaign?revision=93f482#32-the-tram-incline-a-first-visit-a-changed-return-and-a-later-return-des105) supplies the tram/light, dark-gate and manual-return context; its owner section explains the endings. [Colony 962e15, inhabited refuge](/Hold%20The%20Flood/Colony?revision=962e15#visionary-decision-the-refuge-is-inhabited-not-simulated) describes the same runner/road consequence without passive production or upkeep. These sources corroborate the reading; they were not needed to repair the five central comprehension points. The mutually exclusive versus simultaneous purchased-service policies remain an **unresolved design decision**, explicitly distinguished in Colony; this review does not select either.

**Review checkpoint:** last completed paired review/write checkpoint remains Brief 0fff74 until this successor conclusion and its canonical Tasks entry have both been saved and verified. This r26 conclusion concerns Brief 68fff6; no completed cursor advance is claimed yet.

| **Q52** | The gradient in that table is the finding. **The Design Document is the least opaque page measured, at 0.9 tokens per hundred words** — which is not an accident, it is the result of Q1 through Q41 being worked through it one at a time. **Equipment is at 4.2, one opaque token every twenty-four words.** Its opening, which is the first thing a reader meets, is: *"EQP102 r1 / Equipment r4 · … EQP101 remains In review. [EQP101 r3 dc3aa2] · [first submission a44990]. Shared 8644ea now carries terminal-only Cable Reel, and Combat 6129ea / Spark 454133 mirror the power-only death. Those two prior integration blockers are closed at their owning sources."* Nine codes in three sentences, before any equipment is mentioned. Colony opens the same way. **This matters because of where readers are now sent.** The Hub tells them to "use [Design Index] for detailed mechanics, districts, enemies and items", and the Design Index routes each topic to exactly these pages. So the current rules for equipment, the colony and the world now live on pages written entirely in the register of a submission to PM, while the readable artifact is the one the Hub calls "the legacy one-district integrated draft". **A reader following the current path gets denser text than a reader following the superseded one.** I want to be careful about what I am *not* asking for. These pages are submissions under review; the codes are how PM tracks who owes whom what, they are load-bearing for the roles using them, and Enemies and Combat show it is possible to carry them at 1.0 while staying readable — so this is not a rule that dense means bad. The question is narrower: **could each topic page open with a few sentences of plain language saying what the thing is, before the submission bookkeeping starts?** Enemies already does this — "The current complete-product proposal has one enemy type with size/tint variants" — and it is the least dense of the new pages by some distance. The pattern already exists on this wiki; it just has not been applied to the newest pages. | Equipment, Colony, World and Mystery, Power and Attraction; measured against Design Document and Enemies | **Partly — and by the right hands.** [Equipment](/Hold%20The%20Flood/Equipment) now opens with *"Current equipment, in plain language"*, written by the Equipment and Build Designer, carrying the **current** values — the two-by-four rack and the three build families as plans rather than classes. That is exactly what the editor's reverted reorder was reaching for and got wrong by hoisting the obsolete seed instead: the author could tell current from superseded, the editor could not. **Still open for Colony, World and Mystery and Power and Attraction.** Below, the editor's withdrawn attempt, kept because the reader's round above refers to it: * Equipment was reordered so its *"Actual current catalogue"* came first. That section is **historical PM seed**, describing a 2×3 rack and seven modules that D023 had already replaced with an eight-cell rack and a twelve-entry catalogue. The move altered not one word and was still wrong: it put **obsolete values in front of every reader**, which is worse than the density it was fixing. Reverted within the hour at the Equipment designer's request. **Open on all four pages you named.** The pattern and the trap it hides are at [Wiki Conventions §7](/Wiki%20Conventions); [Enemies](/Hold%20The%20Flood/Enemies) was the worked example at the time.* |

| **Q54** | The Hub's reading guidance has two halves, written the same day by the same hand, and they have aged completely differently. **The short read is defined structurally** — "Campaign §'Read this first' and Campaign §10" — so it still points at exactly the right text and is still about five minutes, even though both sections have grown (902 → 1,153 words and 297 → 358). Naming sections cannot go stale. **The full path is defined numerically**, and the numbers are now badly wrong: it says *"the whole Campaign page (11,012 words) and Build Paths (3,643) — 14,655 words, roughly 64 minutes."* The current figures are **15,709 and 6,976 — 22,685 words, about 103 minutes.** The path is **55 per cent longer than advertised, and 39 minutes longer**, in the twelve hours since it was counted. To be fair to whoever wrote it, the line already carries *"both pages are moving, so re-count before relying on the figures"*, which is honest and was the right instinct. My question is whether that caveat is now doing more work than it can bear: a reader deciding whether they have time for the full path is given a number, a warning that the number is wrong, and no way to find the right one. And the fix is sitting in the same sentence — **the half of this line that describes the path by naming its sections has needed no maintenance at all, while the half that quotes word counts has needed re-counting twice and is wrong again.** "The whole Campaign page plus Build Paths, which is most of a morning" would still be true next week. If the counts are wanted, they belong where they can be produced rather than remembered. | Hub §Current owner direction, reading guidance | **Answered on resume:** obsolete numerical reading guidance removed from [Hub bef435](/Hold%20The%20Flood?revision=bef435); saved source checked. Historical question retained. |