2026-09-06 19:38:43
Anonymous:
PMU004: prioritize expanded campaign and topic migration; assign existing roles and mark four proposed roles unstaffed
hold the flood/tasks.md ..
@@ 1,5 1,29 @@
# Hold the Flood — Design Tasks
+
## Current direction — PMU004 owner expansion request
+
+
This section supersedes the older one-district full-product scope and the PMR003 instruction "No new document or mechanic catalogue". The owner finds three to four hours far too little and requests many more districts and proper mechanic/enemy/weapon pages. See [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) and [Design Index](/Hold%20the%20Flood/Design%20Index). Eight districts is PM's planning proposal; a campaign duration must be justified, not promised by multiplication.
+
+
| ID | Owner | Evidence-backed state | Next bounded deliverable |
+
| --- | --- | --- | --- |
+
| OWN101 | Owner | Steering received, not full approval | Premise described as promising; one-district/3–4h product rejected. Scope direction is recorded in Brief D019 |
+
| DES104 | Existing canonical Lead (D014) | Ready — highest-priority integration assignment | Campaign proposal: distinct district roles and progression, three detailed contrasting districts, early/middle/late combat and builds, a substantive colony loop and a spanning mystery. Use topic pages; shorten the owner-facing narrative. Start structure and shared-rule contract now; do not wait for new agents to acknowledge |
+
| WLD103 | Existing World and Mystery Designer | Ready | Expand local mystery into a campaign thread: central question, evolving hypotheses, evidence across districts, later knowledge enabling a meaningful return, fail-safe essential clues and a campaign payoff. Reassess current relay ending as local resolution. Coordinate campaign geography with Lead and proposed Campaign designer |
+
| EDT102 | Existing Wiki Editor, with domain authors | Ready — populated starting pages supplied by PM | Validate and migrate detailed rules/content through Design Index's protocol; create substantive mechanic, enemy, weapon and district pages, with one authoritative owner per rule. Replace duplicated details with links only with source preservation and author coordination. Report coverage gaps; do not invent content or chase a page quota |
+
| CAM101 | Proposed Campaign and District Designer | Blocked — role not yet created | Eight-district planning proposal, recommended count, progression map, three detailed district designs, reasons to return and justified duration assumptions; [opening prompt](/Hold%20the%20Flood/Team/Expansion%20Prompts#campaign-and-district-designer) |
+
| CMB101 | Proposed Combat and Enemy Designer | Blocked — role not yet created | Shared combat grammar, six proposed enemy roles, two mixed encounters and campaign growth; [opening prompt](/Hold%20the%20Flood/Team/Expansion%20Prompts#combat-and-enemy-designer) |
+
| EQP101 | Proposed Equipment and Build Designer | Blocked — role not yet created | Three distinct early/middle/late build paths, substantive weapon/item catalogue, inventory progression recommendation; [opening prompt](/Hold%20the%20Flood/Team/Expansion%20Prompts#equipment-and-build-designer) |
+
| COL101 | Proposed Colony and Progression Designer | Blocked — role not yet created | Campaign-spanning settlement loop, three consequential development strategies, persistence and failure recovery; [opening prompt](/Hold%20the%20Flood/Team/Expansion%20Prompts#colony-and-progression-designer) |
+
| DES103 / REV103 | Lead / Independent Critic | Later submissions received; latest corrections not fully reviewed in PMU004 | GDD [r13 50046f](/Hold%20the%20Flood/Design%20Document?revision=50046f) and REV103 r3 exist; earlier Ready/awaiting-submission labels below are historical. Carry actual unresolved contradictions into domain integration. A corrected short-product document will not by itself satisfy the expanded owner brief |
+
| REV104 | Existing Independent Design Critic | Blocked — expanded integrated submission not yet available | Review DES104's actual revision for owner fit, consistency, distinct content, meaningful growth, mystery coherence and asset burden. Critique available substantive sections as they arrive; no claimed future acceptance |
+
| OWN102 | Owner | Blocked — compelling expanded proposal still required | Owner assessment of the larger design, followed by separate explicit development authorization if desired; design-only gate remains active |
+
+
**Review priority:** move from repeatedly polishing the same short district to developing the missing game. Existing PMR003/REV103 defects still need actual corrections; no automatic closures and no micro-ledger review loop should block parallel campaign drafting. Reader and External Critic should assess the next substantive campaign proposal, using their existing mandates. Researcher may support specific design/asset questions; no extra market-length survey is requested.
+
+
**Staffing:** the four new roles are proposals with ready prompts, not active agents. Existing Lead owns interim domain decisions and can start DES104 immediately. No owner relay or assumption that a posted task wakes another chat.
+
+
## Earlier task sequence and review history
+
Maintainer: PM. Updated: PMR003 integrated-design review, 2026-09-06 UTC. Completed checkpoints are on PM Reviews.
States: Ready, In progress, In review, Accepted, Blocked, Deferred, Superseded.
All three owner-started design agents have submitted work; PMR001 reviewed their actual revisions on 2026-09-06. Task execution and submission are tracked through wiki evidence. PM accepts design work; the owner authorizes a phase change.
