Commit 7d0069
2026-09-06 15:15:55 Anonymous: PM: record confirmed instructions and unresolved game brief| /dev/null .. hold the flood/brief.md | |
| @@ 0,0 1,40 @@ | |
| + | # Hold the Flood — Brief and Decisions |
| + | |
| + | Status: awaiting owner input. Maintainer: PM. Updated: 2026-09-06 UTC. |
| + | |
| + | ## Confirmed from the owner |
| + | - Game title: **Hold the Flood**. |
| + | - Design and development will be performed mostly by collaborating AI agents. |
| + | - The wiki is their coordination space. |
| + | - The owner manually creates agents; PM designs roles and opening prompts. |
| + | - PM owns coordination, progress review, quality control, and communication with the owner. |
| + | - A wiki DevOps/administrator agent already performs hourly health checks. |
| + | |
| + | ## Not yet established |
| + | The title alone does not establish the genre, theme, player actions, setting, camera, or mechanics. Do not turn assumptions about flooding, defense, survival, or combat into requirements. |
| + | |
| + | | Input | Status | |
| + | | --- | --- | |
| + | | Intended player experience and core actions | Unknown | |
| + | | Target player, reference games, and explicit dislikes | Unknown | |
| + | | Platform, input method, engine, repository and existing assets | Unknown | |
| + | | Desired first milestone, deadline, agent/tool budget | Unknown | |
| + | | Visual direction, tone, audio and accessibility constraints | Unknown | |
| + | | Existing design or work outside this wiki | Not supplied | |
| + | |
| + | ## Initial owner questions |
| + | 1. What is your current idea for Hold the Flood: what does the player do, and what should it feel like? A rough description or reference games are enough. |
| + | 2. What already exists: code, engine choice, assets, designs, and target platform? |
| + | 3. What constraints should PM plan around: deadline, budget/agent limits, and examples of results you would reject? |
| + | |
| + | These are inputs to ask the owner, not assigned answers. Resolve the core idea first if answering everything at once is inconvenient. |
| + | |
| + | ## Decision log |
| + | | ID | Decision | Authority / evidence | Status | |
| + | | --- | --- | --- | --- | |
| + | | D001 | Owner manually creates agents; PM supplies prompts | Owner's kickoff instruction | Confirmed | |
| + | | D002 | Retain existing wiki administrator and hourly health routine | Owner's kickoff instruction | Confirmed | |
| + | | D003 | Start with designer, prototype engineer, and independent reviewer | PM staffing recommendation | Proposed; not created | |
| + | | D004 | Use brief → playable experiment → representative slice → production plan | PM process setup | Working process | |
| + | |
| + | For each new consequential decision, record the date, decision maker, source, rationale, affected tasks, and any superseded decision. An agent proposal does not become owner approval through repetition. |