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

| Reviewer | Focused review in project chat | Review each verified submission as it arrives and their interface together; inspect agency, evidence, local failure outcomes, supply/carrying costs and the actual colony transition. |

Both drafts and the focused review are complete and their actual sources verified. One coordinated response is active: clarify air handover, reachable fallback and repeat attempts, align death by phase, and state route and upgrade assumptions. No article is accepted yet. The reviewer independently prepares the next ordinary-horde comparison while authors respond; the authors do the same after submitting their corrections. Those first positions remain private until all are saved and PM releases them together.

The authors work concurrently. Systems posts the small shared contract early while Lead develops character, choices and the home consequence. Each edits only their owned article, checks the latest relevant chat before declaring a dependency missing, and verifies the shared interface before final submission. One self-check belongs in the assignment; there is no extra PM gate after each preparatory step.

The reviewer is already assigned to the named forthcoming submissions. Once an actual verified source arrives, review can begin without another PM permission step. The independent starting position remains preserved. After the focused review, PM inspects the findings, assigns one combined reasoned author response where needed, then makes a provisional disposition or relays a necessary owner preference. No review until unanimity is planned. The original assignment140, unchanged first positions138–139, review144 and bounded response145 are in project chat;146 assigns the reviewer’s independent next comparison.

No global survivor-permadeath rule is settled. The example must state its own local failure consequence rather than substituting "unresolved" for a rule or silently granting immunity. If its concrete crisis needs an owner choice, ask with the actual alternatives and costs while independent work continues. Neither a complete colony economy nor the central mystery's answer is needed for this milestone.

- [Expedition Proposal](/Hold%20The%20Flood/Expedition%20Proposal) and [Build Comparison](/Hold%20The%20Flood/Build%20Comparison): a provisional sortie with observed glyph evidence, contrasting equipment/cargo builds, carrying choices and a survivor interpreting a player-shown clue. The particular notebook use and survivor contribution do not prohibit other uses or cast roles. The comparison's inspection and activation wording now matches the later build rules.

The foundations milestone closed after review125, coordinated responses and final PM consistency edits, disposition137. Article ownership is Lead for Expedition, Exploration and Death; Systems for Build Comparison, Build Rules and Oxygen. No further broad foundations review is pending. Their working proposals can be reopened for a concrete contradiction, owner preference or later authorized evidence.

A useful design preserves the astronaut, hostile station, limited carried oxygen, unexplained revival and growing authored colony. It gives clear information and immediate options while leaving room for open-ended exploration and discoveries about people, history and mechanisms. Builds may become spectacular without manufactured symmetrical weaknesses. Requirements, proposals, dependencies and observations must remain distinct.

The revival cause, station history, escape solution, language details, full rescue/colony systems, exact equipment economy, numerical oxygen rules and campaign content scope remain open. The 30/90/100–200 hour ambitions remain unproven. No implementation, simulations, prototypes, playtests or game assets are authorized.

PM coordinates ready handoffs during active sessions, with one-minute scheduled checks as a fallback while useful authorized work remains. Hourly checks apply only when no such work can continue. The [Team](/Hold%20The%20Flood/Team) page records the working agreement. Add specialist capacity only for a concrete useful need; duplicate work and idle queues are not progress.