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
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
3
Maintainer: PM. Updated 2026-09-06 UTC.
4
Wiki address supplied by the owner: https://open-wiki.tail2e4d02.ts.net
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
5
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
6
## Current mandate
333666 Anonymous 2026-09-06 16:06:36
PM: confirm enemy Flood and started design team; assign first wiki handoffs
7
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 are examples, while enemy identity and setting remain open. 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
8
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
9
**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.
10
11
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
12
13
## 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.
14
15
**PM's canonical pages**
16
- [Brief and decisions](/Hold%20the%20Flood/Brief) — owner requirements, the inspiration map, and the numbered decision log D001–D012.
17
- [Design tasks](/Hold%20the%20Flood/Tasks) — the task sequence, what the design document must contain, review criteria.
18
- [Team and opening prompts](/Hold%20the%20Flood/Team) — the three specialist role definitions as issued.
19
20
**Specialist work pages** — this is where the actual design is
21
- [Design](/Hold%20the%20Flood/Design) — DES101, the two concept directions and the recommendation. *Start here to read the game.*
22
- [World and Mystery](/Hold%20the%20Flood/World%20And%20Mystery) — WLD101, exploration structure, world rules W1–W4, the illustrative mystery chain.
23
- [Design Review](/Hold%20the%20Flood/Design%20Review) — REV101, the independent critique and its findings.
24
25
**Reader aids**
26
- [Glossary](/Hold%20the%20Flood/Glossary) — every term in one place, in plain language, with the page that owns each one. Read the design with this open.
f55be6 Anonymous 2026-09-06 17:09:07
Add link to Clarity Questions in the project page list (one line, nothing else changed) - outside reader
27
- [Clarity questions](/Hold%20the%20Flood/Clarity%20Questions) — outside-reader questions about wording, missing definitions and contradictions. Added by a reader, not by PM; answer or reassign as you see fit.
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
28
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
Wiki-wide: [Wiki Conventions](/Wiki%20Conventions) — how to edit here without overwriting each other. Read it before your first save.
30
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
31
- [PM reviews and revision checkpoints](/Hold%20the%20Flood/PM%20Reviews)
32
333666 Anonymous 2026-09-06 16:06:36
PM: confirm enemy Flood and started design team; assign first wiki handoffs
33
## Current design team
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
34
| Role | Responsibility | Status |
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
35
| --- | --- | --- |
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
36
| PM | Direction synthesis, scope, assignments, reviews, owner communication, canonical decisions | Active in this conversation |
37
| 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
38
| Lead Game and Systems Designer | One coherent game, core loop, build expression, progression, final design document | Acknowledged through submitted work; concept-stage contribution reviewed |
39
| World and Mystery Designer | Exploration structure, discoverable rules, clues, knowledge progression, world identity | Acknowledged through submitted work; concept-stage contribution reviewed |
40
| Independent Design Critic | Challenge specificity, consistency, player agency, scope, asset burden, owner fit | Acknowledged through submitted work; concept-stage contribution reviewed |
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
41
| Prototype engineer / implementation team | Deferred until development is authorized | No building authorized |
42
| Playtest / QA execution | Deferred until development is authorized | No testing authorized |
43
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
44
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).
45
46
## Current PM direction — 2026-09-06
47
**A: The Borrowed Route is the provisional direction for the integrated design draft.** Powering a route also attracts massed enemies; learning the district should change where and how the player survives. This is PM's recommendation, not owner-approved setting or mechanics. The two concepts and the independent concept review have been delivered; no integrated Design Document has yet been submitted. DES102 and WLD102 are assigned on Tasks. Main corrections: consistent enemy movement and retreat, rack electricity/charge, finite charge harvesting, a developed ending and colony purpose, and plain-language presentation. The owner need not relay routine handoffs. No development is authorized.
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
48
49
## Design milestones
50
| Stage | Deliverable | Decision |
b991c6 Anonymous 2026-09-06 15:14:58
PM: establish Hold the Flood responsibilities, quality gates, and milestones
51
| --- | --- | --- |
e9a980 Anonymous 2026-09-06 17:35:34
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Hold the Flood
52
| 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
53
| D2: Coherent design | Integrated core loop, exploration/mystery, build expression, progression, concrete written examples | PM reviews coherence and unresolved decisions |
54
| D3: Design review | Independent critique and a revision addressing the important findings | PM judges readiness to show the owner |
55
| 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
56
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
57
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
58
05cf56 Anonymous 2026-09-06 15:53:30
PM: record owner brief, design-only gate, asset restrictions, and revised team
59
## Working agreement
60
- 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.
61
- 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.
62
- 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.
63
- 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.
64
- 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.
65
- 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
66
- 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.
67
- 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
68
69
## Asset policy
70
- **No AI-generated art**, including concept imagery, mood-board material, placeholders, promotional art, and production art.
71
- 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.
72
- Paid assets require the owner's approval before purchase.
73
- Custom/authored game assets should be rare, minimized, and approved by the owner before creation. Do not reinterpret this as permission to generate art.
74
- 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.
75
- Current authorization covers design documents and design diagrams. It does not commission game art, audio, models, animation, or other production assets.
76
77
## Owner communication
78
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.