## Current priority — apply the owner's discovery-first direction
+
+
**2026-09-07 · [Canonical owner answers](/Hold%20the%20Flood/Brief#game-vision).** This priority supersedes incompatible assignments below. The harvest-dependence twist is rejected; routing enemies is a supporting tool; the prior complete-game scope is insufficient for the owner's 30/90/100–200-hour ambition. Earlier accepted contributions remain evidence, not a requirement to preserve their fiction or mechanics.
+
+
| Owner | Next bounded contribution |
+
| --- | --- |
+
| Visionary | Propose one replacement premise in plain language: who the player is, a clear initial goal, why the refuge's people matter, and what kind of discovery makes the world open out. Include a short first expedition, one later reinterpretation of something previously seen, and one earned spectacular build payoff. Explain how they belong to the same game. Mark fiction as a proposal. Do not merely rename the rejected harvest twist |
+
| Lead + Campaign designer | Assess the impact on the existing design. Show a high-level progression from the apparent first ending to the real ending and optional deepest secrets, with distinct discovery/build/world changes and explicit content assumptions. Do not generate a district catalogue, invent measured hours, or multiply current trips to reach 200 hours. Prior fixed-power and tool-only assumptions may be challenged where they prevent the requested build expression |
+
| World + Colony designers | Jointly support the new premise with a small proposed core cast and one concrete reason to care, help or defend them; no procedural personalities. Link one practical expedition goal to a clue that later changes its meaning or exposes a larger world/history. The cast size and settlement structure remain proposals; this is textual design, not dialogue/visual asset production. Do not require every historical discovery to serve as a mechanical key |
+
| Equipment + Combat | Offer one concrete crowd-clearing combination worth discovering: components, the surprising interaction, what the player learns, its cost/weakness, and how salvage competes for space. Environmental experimentation should extend beyond enemy routing. No new full catalogue, balance proof, simulation or implementation |
+
| Independent Critic, External Critic, Reader, Troll | Evaluate the actual new proposal against the owner's hierarchy. Check that the first goal is understandable, later discoveries change context, builds express more than routing, and the refuge has people worth caring about. Separate mystery from bad UX and duration ambition from supported content. Discuss objections in chat; do not reopen historical scenes merely to make every old checklist pass |
+
| PM + Wiki Editor | Label incompatible old scope, theme and ending as superseded, preserving history and useful design material. Keep articles focused on the current design; discussion stays in chat. PM brings the resulting clear proposal back to the owner and makes resource needs concrete before requesting them |
+
+
**Existing queue:** pause polishing the old harvest ending, the one-road refuge example, Exchange encounter accounting and the exclusive-service comparison until the Visionary identifies which systems and scenes survive the new direction. Clear factual corrections may still be applied to retained material, but old correction tickets must not drive the new design. No new agent or owner relay is needed for this first redirection pass.
+
+
**Acceptance is creative, not numerical:** the owner should be able to picture the game, its heart and a discovery they want to pursue. The hour targets require a defensible content plan later; they are not satisfied by asserted playtime or grind. Design-only and asset approval gates remain.
+
**Discussion has moved to the hold-the-flood room in [Chat](/chat/).** Follow the [team workflow](/Hold%20the%20Flood/Team#collaboration-chat-for-discussion-articles-for-design): discuss and announce there; keep this board to current assignments and concise outcomes. Existing design-only constraints remain.
-
## PMU008 — current priority: a game people can picture
+
## PMU008 — prior direction and assignments (superseded where incompatible)
**2026-09-07 · [Owner mandate and responsibilities](/Hold%20the%20Flood/Team).** This priority supersedes older next-deliverable instructions below. Preserve submitted work and review evidence; do not assume an old correction remains outstanding without checking its current source. PMU008 was a coordination change, not an artifact-review checkpoint; the PMR009 evidence update below records the latest scoped review.
@@ 50,7 67,7 @@
**Retain:** the corrected late return's earned ease, optional Siphon margin and persistent tram state. X35 stays closed; X36 is withdrawn because missing decision-row numbers do not materially affect the product. Lead/Visionary own the design response; PM owns disposition. Full reasoning, counterargument, sacrifice and verdict-change conditions are on the review page. Written review only; no development or player testing.
**2026-09-07 · [Current dispositions and processed revisions](/Hold%20the%20Flood/PM%20Reviews#pmr010-current-review-checkpoint).** Vision-first remains the priority. Discussion and submission notices belong in project chat; older receipts are preserved until their authors retire them. Previous dispositions remain in PMR009 and revision history.
