**Verdict: the owner-set premise is clear enough as a premise, but its intended first-sortie explanation has not yet been supplied.** [Brief ab030a, “the astronaut and the unofficial space station”](/Hold%20The%20Flood/Brief?revision=ab030a#game-vision) clearly establishes the player, forced arrival, oxygen constraint, hostile horde, revival mystery, survivor colony and station mysteries. It explicitly leaves the first objective and connected expedition design open. A reader can explain the premise and threat, but cannot yet retell the repeated play, consequential choices or changed return without inventing the assigned next delivery. This is a bounded unresolved design deliverable, not a prose ambiguity.

**Artifact and audience:** Brief ab030a's canonical owner-set Game vision, intended to state the premise for the owner, designers and a newcomer; its owner-facing first-sortie design is explicitly the next delivery. Compared with the last successfully reviewed artifact, [Brief 51e58b](/Hold%20The%20Flood/Brief?revision=51e58b#latest-owner-correction-survivorlike-identity-and-songs). The intervening Hearth foundation and earlier World Below/Tram scenes are not substituted for the station sortie.

**Reading conditions:** I am the continuing reviewer with accumulated knowledge of earlier Brief, Campaign, Hub and World Below/Hearth revisions. Project-room messages 63 and 65 made the premise change visible before the canonical save. I then read the actual Brief ab030a alone, without the glossary, and recorded the account below before consulting current Tasks. This is not a fresh-context test and does not claim that an actual newcomer understood it.

**Explicit:** You are an astronaut whose broken ship forces you to dock at an unofficial station broadcasting “stay away!” and refusing hails. Away from the ship, oxygen is limited and canisters can be found; the ship produces unlimited oxygen, and oxygen depletion kills. Zombies and other creatures attack on sight, damage can kill, and death returns the astronaut to the ship for an unexplained reason. Human survivors can be sent to the ship to form a small colony. The station contains puzzles, traps, mechanisms and at least two alien languages. Immediate goals and survival information must remain clear, while the first sortie, rescue process, build development, persistence and mystery answers are explicitly open design work.

**Inferred:** the ship is the hub for repeated station sorties, and survival, escape, survivors and the revival/station mysteries can motivate returns. That shape follows naturally from the premise, but the page has not yet selected the first practical objective or demonstrated how oxygen, horde pressure, builds, clues and rescue combine in play.

**Could not determine:** the astronaut's first practical objective after docking; what one complete sortie repeatedly asks them to do; how oxygen, health, equipment, salvage and retreat compete; what death preserves; how a survivor reaches the ship; what two build choices change; or the concrete changed state that makes the next sortie different. The Brief names each as an open design decision and assigns a connected first-sortie design. No specialist scene supplies that missing owner-facing artifact.

- **Who and what they want:** an astronaut forced to dock is clear; immediate survival is explicit, while the first practical objective and route to leaving are open.

**Passage:** “Tasks assigns one connected first-sortie design” and the open-decision list names “a clear first practical objective,” oxygen/death persistence, build development, rescue and progression. **Plausible reading:** the page is intentionally premise canon plus a design brief, not yet the explanation of an expedition. **Why it matters:** the premise answers who and what threatens them, but an owner/newcomer cannot yet explain what the player repeatedly does, which choices change the run or why the next sortie differs. **Focused missing explanation:** supply the assigned connected first sortie and changed return, with a clear immediate goal and the proposed links among oxygen, horde/build choices, one discovery, survivor contact, retreat or death, persistence and the next purpose. This repeats the canonical assignment rather than inventing mechanics.

**Supporting follow-up:** [Tasks c46f17](/Hold%20The%20Flood/Tasks?revision=c46f17#current-priority-integrate-the-owner-set-space-station-premise) confirms the first integrated sortie and changed return are due and assigns their component questions. Room message 63 announced the owner premise and message 65 describes superseded Hearth work; the actual Brief ab030a, not either room claim, grounds this verdict.

**Checkpoint pending paired write:** selected artifact Brief ab030a; this premise conclusion advances only after Clarity Questions and canonical Tasks both save and verify. Room messages 63–65 are handled, but the cursor advances only with the completed paired record.

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