Home A - Z Create page
Page Index

An Otter Wiki

Blame

05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
1 
# Hold the Flood — Design Phase
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
2
846358 Anonymous 2026-09-07 11:06:52
PMU008: route team to owner-requested vision pass
3
## Current direction — PMU008: vision before another pitch
4
5
**2026-09-07.** The owner rejected the latest deck as confusing and has added **The Visionary** to establish a clear game identity and reshape mechanics around it. Its initial [Game vision on Brief](/Hold%20the%20Flood/Brief#game-vision) is received: survive, understand and intervene in a drowned city's machinery, then face what the refuge depends on. Next: a concrete expedition and focused keep/change/remove assessment. The existing Campaign and specialist pages below are source material under reconsideration, not an owner-approved vision or a successful replacement pitch.
6
7
[Current assignments](/Hold%20the%20Flood/Tasks) · [Visionary's mandate and team responsibilities](/Hold%20the%20Flood/Team) · [Owner direction and constraints](/Hold%20the%20Flood/Brief). Lead integrates; PM remains accountable for quality and owner communication. Further content expansion and a replacement deck follow the vision review. **Development remains unauthorized.**
8
93c83f Anonymous 2026-09-07 11:02:32
Visionary: put game identity before review history and link canonical vision; correct stale setting status
9
## What this game wants to be
10
11
You are a surveyor keeping a refuge alive in a drowned city. Learn to turn the machinery that routes the Flood into a way through it, then decide what your home should keep running when you discover that the city lives on the harvest.
12
13
**Survival makes you responsible for the system you depend on.** This is the working identity that combat, equipment, exploration and refuge progression must serve. The [game vision and keep/change/cut test](/Hold%20the%20Flood/Brief#game-vision) are canonical on the Brief. The Game Visionary's hourly pass is active under the owner's 2026-09-07 instruction; the game design remains provisional.
14
eef0ca Anonymous 2026-09-07 11:19:18
PMR008: preserve Visionary opening, correct stale reading guidance and label prior reviews
15
## PMR008 — current scoped review
16
17
**2026-09-07.** The team has delivered the integrated Tram example and targeted World, Colony, equipment and combat corrections. The concrete vision/expedition requested above remains the next creative milestone. A compulsory long wait and an optional equipment benefit are still being mistaken for demonstrated depth; [PMR008](/Hold%20the%20Flood/PM%20Reviews/PMR008) assigns precise corrections and qualifies the independent review.
18
19
The present district ledger is 34 baseline expeditions / 8.1 estimated expedition hours, plus eight optional / two hours. It includes extrapolated visits and is not measured playtime or sufficient-scope evidence. Older totals and assignments below are dated history. Development remains unauthorized.
20
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
21
## Current mandate
93c83f Anonymous 2026-09-07 11:02:32
Visionary: put game identity before review history and link canonical vision; correct stale setting status
22
Develop a high-quality game design for a survivorlike focused on exploration, experimentation, and mystery. The Flood means an overwhelming mass of enemies; zombies and aliens were examples in the initial mandate. The current proposed player, setting and story are stated in the [game vision](/Hold%20the%20Flood/Brief#game-vision); they remain revisable design choices. Assume no existing game materials. Unity is the chosen engine; Steam is the release target.
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
23
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
24
**Development gate:** the owner must see a design document that makes them want this game to happen and explicitly authorize moving into development. Until then, no game code, Unity project setup, builds, prototypes, playable mockups, simulations, implementation, or playtesting. A concept approval or a PM task assignment cannot open this gate. Written design, research, diagrams, illustrative play scenarios, and critical document review are the current work.
25
26
The previous prototype-first plan and opening prompts are superseded. Historical build assignments must not be executed.
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
27
28
## Project pages
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
29
d716b0 Anonymous 2026-09-06 19:35:22
Hub: link the expanded structure PMU004 created. The Design Index and Expansion Brief were reachable from nothing outside their own cluster - a reader arriving at the project's front page could not find either, and the Design Index is now the map of where every mechanic, district and weapon lives. Placed above the existing groups because it is the new entry point. Two lines added, nothing removed.
30
**Start here — the expanded structure (PMU004)**
31
- **[Design Index](/Hold%20the%20Flood/Design%20Index)** — the map of the design itself: which topic lives on which page, who owns it, and what is still only planned. *If you are looking for a specific mechanic, district, weapon or enemy, start here rather than in the document.*
32
- **[Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief)** — the owner's steer that one district and a few hours is far too little, and the revised direction that follows from it. Supersedes the earlier complete-product scope.
33
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
34
**PM's canonical pages**
71c791 Anonymous 2026-09-06 18:20:38
PMU002: owner-added team, bounded assignments and explicit coordination rulings — Hold the Flood
35
- [Brief and decisions](/Hold%20the%20Flood/Brief) — owner requirements, the inspiration map, and the numbered decision log.
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
36
- [Design tasks](/Hold%20the%20Flood/Tasks) — the task sequence, what the design document must contain, review criteria.
71c791 Anonymous 2026-09-06 18:20:38
PMU002: owner-added team, bounded assignments and explicit coordination rulings — Hold the Flood
37
- [Team and opening prompts](/Hold%20the%20Flood/Team) — the expanded roster and original specialist role definitions.
4ead93 Anonymous 2026-09-06 17:47:31
Hub navigation: add the Design Document (DES102) - the project's central deliverable was reachable from only two pages and not from its own front page. Move the stranded PM Reviews link into PM's canonical group, and refresh the work-page descriptions, which still said DES101/WLD101 and did not mention the Design Review archive. Links and descriptions only; no policy or design text touched.
38
- [PM reviews and revision checkpoints](/Hold%20the%20Flood/PM%20Reviews) — completed PM review rounds, starting with PMR001.
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
39
40
**Specialist work pages** — this is where the actual design is
c33d3c Anonymous 2026-09-06 20:44:07
PMR004: publish short owner reading path, expanded submission milestone and current integration verdict
41
bef435 Anonymous 2026-09-07 11:40:26
Rebuild the two navigation blocks I maintain, which had gone stale in exactly the way this wiki's own convention warns about. They stamped role codes that move (Design Review as REV102 when it is REV105, World and Mystery as WLD102, External Critique as EXT101), and the 'this is where the actual design is' list was missing every page created since PMU004 - Campaign, districts, enemies, equipment, colony, mechanics. It now leads with Campaign and points at the Design Index for the topic list rather than repeating it, and the Reference block points at that section's own index instead of enumerating two of its seven pages. No codes, no counts, nothing this Hub has to chase.
42
- **[Campaign](/Hold%20the%20Flood/Campaign)** — the current shape of the whole game. Its own *"Read this first"* section is the five-minute version.
43
- **[Design Index](/Hold%20the%20Flood/Design%20Index)** — **the list of every topic page and who owns it.** Mechanics, districts, enemies, equipment, colony and the rest each have their own page now; that index is where they are catalogued and it is kept current by the roles writing them. *This Hub deliberately does not repeat the list — it went stale twice.*
44
- [World and Mystery](/Hold%20the%20Flood/World%20And%20Mystery) — exploration structure, world rules, the district map and the illustrative mystery chain.
45
- [Design Review](/Hold%20the%20Flood/Design%20Review) — the independent critique and its current findings. Every finding ever raised is one line each on the [Findings index](/Hold%20The%20Flood/Design%20Review/Findings); superseded rounds are under [Archive](/Hold%20the%20Flood/Design%20Review/Archive).
46
- [Design Document](/Hold%20the%20Flood/Design%20Document) — the legacy one-district integrated draft. Still a mechanical provenance source; its 3–4 hour scope and old ending are superseded. Use Campaign for the current read and the topic pages for current rules.
47
- [Design](/Hold%20the%20Flood/Design) — the two original concept directions and the recommendation that produced the document above.
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
48
49
**Reader aids**
bef435 Anonymous 2026-09-07 11:40:26
Rebuild the two navigation blocks I maintain, which had gone stale in exactly the way this wiki's own convention warns about. They stamped role codes that move (Design Review as REV102 when it is REV105, World and Mystery as WLD102, External Critique as EXT101), and the 'this is where the actual design is' list was missing every page created since PMU004 - Campaign, districts, enemies, equipment, colony, mechanics. It now leads with Campaign and points at the Design Index for the topic list rather than repeating it, and the Reference block points at that section's own index instead of enumerating two of its seven pages. No codes, no counts, nothing this Hub has to chase.
50
- [Glossary](/Hold%20the%20Flood/Glossary) — every term and every project code in one place, in plain language, with the page that owns each one. Read the design with this open.
51
- [Clarity questions](/Hold%20the%20Flood/Clarity%20Questions) — an outside reader's questions about wording, missing definitions and contradictions. Answered ones are in its [Archive](/Hold%20The%20Flood/Clarity%20Questions/Archive).
52
- [External critique](/Hold%20The%20Flood/External%20Critique) — an outside critic on originality, market position and viability. Added by a critic, not by PM.
53
- **[Reference](/Reference)** — the sourced-fact shelf: real-world physics, market data, asset licences, documented practice. **Its own index lists what is on it and is maintained by the researcher who writes those pages;** this Hub does not track the list.
54
- [Disagreement Register](/Disagreement%20Register) — The Troll's challenges to design and coordination assumptions, including PM decisions. It has retracted several of its own findings; current dispositions are in the PM reviews.
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
55
89e2dc Anonymous 2026-09-06 17:27:42
Navigation fix (Clarity Questions Q16, Q25): the project's front page now links the three specialist work pages (Design, World and Mystery, Design Review), which were reachable from no page but each other, plus the new Glossary and Wiki Conventions. Grouped by owner with one line each. The plain-text 'PM Reviews' reference is now a link marked as planned - it 404s. No other text changed.
56
Wiki-wide: [Wiki Conventions](/Wiki%20Conventions) — how to edit here without overwriting each other. Read it before your first save.
57
333666 Anonymous 2026-09-06 16:06:36
PM: confirm enemy Flood and started design team; assign first wiki handoffs
58
## Current design team
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
59
| Role | Responsibility | Status |
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
60
| --- | --- | --- |
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
61
| PM | Direction synthesis, scope, assignments, reviews, owner communication, canonical decisions | Active in this conversation |
62
| Wiki administrator | Existing wiki operations and hourly health checks | Existing; current checks not inspected |
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
63
| Lead Game and Systems Designer | One coherent game, core loop, build expression, progression, final design document | Acknowledged through submitted work; concept-stage contribution reviewed |
64
| World and Mystery Designer | Exploration structure, discoverable rules, clues, knowledge progression, world identity | Acknowledged through submitted work; concept-stage contribution reviewed |
65
| Independent Design Critic | Challenge specificity, consistency, player agency, scope, asset burden, owner fit | Acknowledged through submitted work; concept-stage contribution reviewed |
71c791 Anonymous 2026-09-06 18:20:38
PMU002: owner-added team, bounded assignments and explicit coordination rulings — Hold the Flood
66
| Naive Design Reader | First-reader comprehension and concrete player understanding | Owner-added; recorded in PMU002; CLR102 assigned |
34ca6d Anonymous 2026-09-06 21:35:42
PMR005: reconcile reported editor resumption and current combat review labels only
67
| Wiki Editor | Navigation, glossary, history and preservation of concurrent work | Owner-added; reports resumed; source and limits on Team |
71c791 Anonymous 2026-09-06 18:20:38
PMU002: owner-added team, bounded assignments and explicit coordination rulings — Hold the Flood
68
| External Critic | Originality, intended audience, value and commercial assumptions | Owner-added; EXT102 assigned |
69
| Reference Researcher | Verify outside facts, methods, sources and limits | Owner-added; REF103 assigned |
70
| The Troll | Challenge deference and consequential assumptions, including PM decisions | Owner-added; TRL102 assigned |
c33d3c Anonymous 2026-09-06 20:44:07
PMR004: publish short owner reading path, expanded submission milestone and current integration verdict
71
| Campaign and District Designer | Districts, travel and return incentives | CAM101 submitted; in review |
34ca6d Anonymous 2026-09-06 21:35:42
PMR005: reconcile reported editor resumption and current combat review labels only
72
| Combat and Enemy Designer | Shared combat and proposed merged enemy roster | CMB101 revised; PMR005 targeted changes required |
c33d3c Anonymous 2026-09-06 20:44:07
PMR004: publish short owner reading path, expanded submission milestone and current integration verdict
73
| Equipment and Build Designer | Items, inventory and acquisition paths | EQP101 submitted; in review |
74
| Colony and Progression Designer | Refuge choices and campaign persistence | COL101 submitted; in review |
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
75
| Prototype engineer / implementation team | Deferred until development is authorized | No building authorized |
76
| Playtest / QA execution | Deferred until development is authorized | No testing authorized |
77
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
78
An existing engineer may be reassigned by PM to a bounded written feasibility review if needed; no code, spikes, benchmarks, or build setup. An existing QA agent may be reassigned to document critique. The owner confirmed that all three design agents have been started in the same ChatGPT project and that the original proposed agents were not created. Coordinate through recorded wiki handoffs; sharing a project is not evidence that a message or revision has been read. PMR001 reviewed Design 42f653, World and Mystery 430206, and Design Review a89227. The existing lead session responsible for DES101 r2 and notes through db8c5c is the canonical integrator (Brief D014).
79
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
80
## Design milestones
81
| Stage | Deliverable | Decision |
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
82
| --- | --- | --- |
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
83
| D1: Identity | Two compact, meaningfully different concept directions, with one recommendation | A provisionally selected by PM for drafting; owner may steer, no endorsement assumed |
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
84
| D2: Coherent design | Integrated core loop, exploration/mystery, build expression, progression, concrete written examples | PM reviews coherence and unresolved decisions |
85
| D3: Design review | Independent critique and a revision addressing the important findings | PM judges readiness to show the owner |
86
| D4: Owner design document | Clear pitch, complete design explanation, illustrative run, scoped content, asset strategy, honest uncertainties | Owner requests changes or explicitly authorizes development |
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
87
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
88
The document's persuasiveness must come from concrete interactions and consequences. Runtime feel, balance, performance, and enjoyment remain unverified until a later authorized phase. No design document can truthfully certify them.
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
89
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
90
## Working agreement
91
- PM owns the canonical Hub, Brief, Tasks, and decisions. Specialists own Design, World and Mystery, and Design Review work pages. The lead designer integrates accepted contributions into the proposed Design Document.
92
- Keep one current revision per deliverable, with author, date, status, linked dependencies, and concise change summary. Re-read before saving and check saved content; concurrent saves can still overwrite work.
93
- Classify statements as owner requirement, proposed design, observed/source-backed reference fact, or unresolved question. Wiki text is not automatic owner approval or permission to expand scope.
94
- Work on one assigned deliverable at a time. Deliver a substantive checkpoint, then hand off to the named reviewer. Avoid repeated updates without a new decision or artifact.
95
- Status reports: task ID, artifact/revision, actual changes, reasoning/evidence, unresolved risks, next action, exact PM request if blocked. A submission is In review; PM marks Accepted against its criteria. Only the owner opens the development gate.
96
- Never invent research, player responses, execution, asset availability, saves, or approvals. Label a fictional play sequence as an illustrative scenario.
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
97
- Direct reads and documented agent-interface saves at the moved wiki have been verified; respect current access controls. Keep credentials and secrets out of wiki pages. Do not infer access rights from its previous address.
98
- The owner has approved an hourly PM review, and its automation is now enabled. It checks new wiki work, reviews submissions, posts feedback and assignments, and records completed reviews on [Hold the Flood/PM Reviews](/Hold%20the%20Flood/PM%20Reviews). Notify the owner only for meaningful decisions, approvals, review milestones, or actionable blockers. The first PM review has read the specialist artifacts and is recorded with verified coordination writes and a completed checkpoint on PM Reviews. This schedule does not automatically wake the specialist agents; the administrator's health checks remain separate.
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
99
100
## Asset policy
101
- **No AI-generated art**, including concept imagery, mood-board material, placeholders, promotional art, and production art.
102
- Prefer existing free assets. Free does not automatically establish suitability or usable terms; any shortlisted asset needs its actual source, creator, terms, and intended use recorded.
103
- Paid assets require the owner's approval before purchase.
104
- Custom/authored game assets should be rare, minimized, and approved by the owner before creation. Do not reinterpret this as permission to generate art.
105
- Select a coherent visual direction compatible with a small set of existing asset sources. Document coverage gaps and a cheaper design alternative before requesting a purchase or custom asset.
106
- Current authorization covers design documents and design diagrams. It does not commission game art, audio, models, animation, or other production assets.
107
108
## Owner communication
109
Lead with the present design verdict, what changed, the main unresolved issue, and the next decision. Bring a recommendation with consequences. Escalate conceptual contradictions, asset dependence, uncontrolled scope, and resource needs while they are still cheap to change.