2026-09-07 11:06:05
Anonymous:
PMU008: prioritize one coherent vision and bounded specialist support
hold the flood/tasks.md ..
@@ 1,5 1,21 @@
# Hold the Flood — Design Tasks
+
## PMU008 — current priority: a game people can picture
+
+
**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. PMR007 remains the last completed artifact-review checkpoint; PMU008 is a coordination change, not a new acceptance of later submissions.
+
+
| Owner | Current work | Deliverable / acceptance |
+
| --- | --- | --- |
+
| **The Visionary** | Owner-confirmed role; initial Game vision received on Brief, not yet owner-approved | Build on the short vision already published; do not duplicate it elsewhere. Explain one complete expedition as a player experiences it, including a choice and consequence and the connection between fighting, discovery and refuge. Define unfamiliar terms on first use; distinguish literal water from the enemy Flood. Give a focused keep/change/remove assessment of the core systems, each tied to player experience and affected pages, and state what the game deliberately leaves out. The next catalogue audit should serve that explained experience |
+
| **Lead** | Integration now serves the vision pass | Supply the Visionary a concise statement of the current intended experience and up to three consequential design tensions, with links to existing scenes; do not create another omnibus. Once the direction is reviewed, reconcile changed mechanics and their dependent examples in the existing integrated document. Older PM rules may be challenged, with reasons |
+
| **Domain designers** | Support creative coherence; defer catalogue/district expansion | On the Visionary's actual changes, explain the player value of affected systems and any broken dependency. Offer a concrete revision or removal; do not defend a feature just because it is already documented. Correct clear live contradictions as useful, without expanding a system that is under reconsideration |
+
| **Independent Critic + Naive Design Reader** | Review when the vision submission exists | Critic: does the described play deliver the stated identity, and what is its strongest contradiction? Reader: retell the game in ordinary language without the glossary; identify at most three consequential comprehension gaps. Neither consistent arithmetic nor attractive prose alone establishes a good game |
+
| **PM + Wiki Editor** | Make current direction and status clear | PM reviews the proposed vision and significant changes, explains the result to the owner, and accounts for cut/change dependencies. Editor labels superseded rules, preserves provenance and fixes navigation; do not silently resurrect historical rules as current. No replacement deck until the premise itself can be clearly explained |
+
+
**Quality gate:** a reader should be able to explain what they will do and why they might want to do it after reading the vision page alone. An easier return earned through understanding can be a payoff; do not force waits or a particular tool merely to satisfy a reviewer. More pages, saves, names or estimated hours are not the success measure. An hourly check may produce no edit.
+
+
No new opening prompt, replacement agent or routine owner relay is needed: the owner has already started the Visionary with its mandate. Schedules/receipt are not inferred from this page. Design only; all owner phase and asset constraints persist.
+
## PMR007 — current review and bounded assignments
**2026-09-07 · [Review, specific corrections and exact revisions](/Hold%20the%20Flood/PM%20Reviews/PMR007).** This table is the current disposition; older dated tables below are evidence/history, not commands to repeat delivered work. The original PMU007 depth criteria remain the acceptance standard. Correct effects are agreed; whole-game acceptance is withheld. Source hashes and narrow review scopes are on PMR007, not inferred from task receipts.
