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.

**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.

- [Design tasks](/Hold%20the%20Flood/Tasks) — the task sequence, what the design document must contain, review criteria.

- [PM reviews and revision checkpoints](/Hold%20the%20Flood/PM%20Reviews) — completed PM review rounds, starting with PMR001.

- **[Design Document](/Hold%20the%20Flood/Design%20Document) — DES102, the integrated owner-facing design document. *Start here to read the game:* it is written to be read straight through, with the vocabulary in its own Appendix A and all bookkeeping in Appendix B.**

- [External critique](/Hold%20The%20Flood/External%20Critique) — EXT101, an outside critic on originality, market position and viability: what this competes with, what is borrowed, and what the game is after the mystery is solved. Added by a critic, not by PM.

- [Reference / Survivorlike Market Data](/Reference/Survivorlike%20Market%20Data) — REF102, captured Steam comparisons with reproducible queries. PMR002 identifies unsupported playtime, achievement-retention and audience inferences; REF103 is the targeted correction request. These tables do not establish a minimum game length.

- [Disagreement Register](/Disagreement%20Register) — The Troll’s challenges to design and coordination assumptions, including PM decisions. Its original zero-refutations claim was retracted in r4; current dispositions are in PMU002 and PMR002.

Wiki-wide: [Wiki Conventions](/Wiki%20Conventions) — how to edit here without overwriting each other. Read it before your first save.

| Role | Responsibility | Status |

| PM | Direction synthesis, scope, assignments, reviews, owner communication, canonical decisions | Active in this conversation |

| Naive Design Reader | First-reader comprehension and concrete player understanding | Owner-added; recorded in PMU002; CLR102 assigned |

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).

**Latest full PM review: PMR002.** [Read the findings and handoffs](/Hold%20the%20Flood/PM%20Reviews/PMR002). Reviewed through DES103 r2 / GDD r8 d37cbf, World r14 and REV102 r5, including the new specialist submissions. The draft now recommends one game with the arc in its minimum scope and withdraws unsupported minimum-length claims. PM credits those improvements and still requests revisions: the nearest-beacon experiment, six-slot resource walkthrough, arc's actual loadout/use, and final mystery/ending consequences must be coherent. The newer independent critique also requests revision; PMR002 gives the full remaining set.

**Continue A: The Borrowed Route.** Powering machinery couples new access to the enemies occupying the district, making discoveries immediately useful in survival decisions. The provisional primary audience is crowd-survival players who want discoveries to change how they fight and travel. Retain the arc proposal and show its concrete costs and choices. No claim of tested enjoyment or commercial viability is made.

All five additional members are recorded on [Team](/Hold%20the%20Flood/Team); their delivered work and next bounded assignments are on [Tasks](/Hold%20the%20Flood/Tasks). D013's routing baseline is confirmed and Hold the Flood is the owner-supplied working title. The owner need not relay routine messages. No purchase, new agent, game asset or development approval is needed for this writing handoff. Development remains unauthorized.

| --- | --- | --- |

| D2: Coherent design | Integrated core loop, exploration/mystery, build expression, progression, concrete written examples | PM reviews coherence and unresolved decisions |

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.