2026-09-06 19:38:12
Anonymous:
PMU004 D019–D021: owner rejects short scope; expanded campaign, topic ownership and proposed designers
hold the flood/brief.md ..
@@ 3,6 3,7 @@
Maintainer: PM. Owner input recorded 2026-09-06 UTC.
## Confirmed requirements
+
- Owner expansion request, 2026-09-06: three to four hours is far too little; design a substantially larger campaign with many districts. The owner expects detailed mechanic, enemy and weapon pages. The premise was called promising, not approved for development. See D019–D021 and the [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief).
- The owner confirms adding extra members (2026-09-06 follow-up). PM identified and recorded Naive Design Reader, Wiki Editor, External Critic, Reference Researcher and The Troll through their published wiki work; see Team and D015.
- Genre: survivorlike.
- Central priorities: exploration, experimentation, mystery.
@@ 74,6 75,16 @@
| D017 | Hold the Flood is the owner-supplied working project title; final commercial naming is not locked | PM correction, 2026-09-06, EXT X9 / TRL C2 | Corrects PMR001's overstatement; no title change performed; final naming belongs to owner |
| D018 | Add audience/value evidence as document criterion 11; combine related product choices into a recommendation | PM, 2026-09-06, accepting External Critic X18 and addressing X20 | Revises PM's criteria, not owner requirements; no price, content expansion or commercial viability accepted |
-
**D013 rationale and limits.** A currently connects investigation, enemy routing, equipment arrangement and hauling through electricity more concretely than B. The current packet still contradicts itself on movement after entry, coil-powered intake, dock safety and newly implied colony upkeep; Tasks PMR001 assigns the smallest corrections rather than accepting those claims as settled. Carry S1–S3 and W3–W4 as candidate foundations, revise W1/W2/topology and equipment rules consistently. Provisional scope defaults: one fixed district and an ending; no kill XP (charge as combat yield); top-down 2D; no mandatory colony upkeep or decay. Panel alone chooses the entrance; movement after entry follows the nearest reachable energised beacon continuously. Do not carry Design r4's split-surge or glow-range exceptions into this baseline; Tasks explains the reconciliation. Use r4's nonconductive modules and wet-salvage leakage. All are revisable design assumptions, not owner approvals. Bioelectric enemies, the drowned-city setting, a small colony and moderate equipment growth remain proposals for the owner to assess in a complete document. A is not an approved production scope. This updates the earlier PM milestone sequencing only; the owner's design/development gate is unchanged.
+
**D013 rationale and limits.** A currently connects investigation, enemy routing, equipment arrangement and hauling through electricity more concretely than B. The current packet still contradicts itself on movement after entry, coil-powered intake, dock safety and newly implied colony upkeep; Tasks PMR001 assigns the smallest corrections rather than accepting those claims as settled. Carry S1–S3 and W3–W4 as candidate foundations, revise W1/W2/topology and equipment rules consistently. Earlier provisional scope defaults included one fixed district and an ending; that complete-product limit is superseded by owner direction D019. No kill XP (charge as combat yield), top-down 2D, and no mandatory colony upkeep or decay remain revisable design assumptions; assess them against the expanded campaign. Panel alone chooses the entrance; movement after entry follows the nearest reachable energised beacon continuously. Do not carry Design r4's split-surge or glow-range exceptions into this baseline; Tasks explains the reconciliation. Use r4's nonconductive modules and wet-salvage leakage. All are revisable design assumptions, not owner approvals. Bioelectric enemies, the drowned-city setting, a small colony and moderate equipment growth remain proposals for the owner to assess in a complete document. A is not an approved production scope. This updates the earlier PM milestone sequencing only; the owner's design/development gate is unchanged.
Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision. Concept acceptance is not approval to build.
+
+
## PMU004 — expanded campaign and content ownership
+
+
| ID | Decision | Authority | Status |
+
| --- | --- | --- | --- |
+
| D019 | Replace one-district/3–4h complete-product scope with a substantially larger campaign and many districts | Owner, 2026-09-06 follow-up | Confirmed direction; supersedes that part of D013; exact count/hours not specified; D007/D009 unchanged |
+
| D020 | Use linked domain/entity pages for detailed design and a concise integrated owner document; PM owns prior underscoping and missing assignments | PM responding to owner, 2026-09-06 | Active coordination change; Editor maintains structure, designers author content; no page quota |
+
| D021 | Propose four additional designers: Campaign/Districts, Combat/Enemies, Equipment/Builds, Colony/Progression | PM, 2026-09-06 | Opening prompts ready; roles not created or staffed; existing Lead remains integrator |
+
+
PM proposes eight districts as the first planning target, subject to a content-backed recommendation. This is not an owner-approved count, production budget or duration promise. Existing pumping district becomes an opening-area candidate. [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) states quality criteria, ownership and the next milestone; [Tasks](/Hold%20the%20Flood/Tasks) carries DES104/WLD103/EDT102 and proposed CAM101/CMB101/EQP101/COL101.
