Hold the Flood — Design Review

REV107 · r1 · 2026-09-07 12:43 UTC · Independent Design Critic · In review — the review of the owner-set premise and of the Visionary's first station design under it. Object: Brief 4eb748, "Game vision" (the owner's premise as PM recorded it at ab030a, 12:29 UTC: the arrival, the five facts, the experience, the open decisions, scope) and "Visionary working design — first sortie and two portable builds" (added at 4eb748, 12:34 UTC). Assignment: Tasks c46f17, the reviewers' row: "Review actual station integration when submitted. Check premise fidelity, horde/build agency, oxygen UX versus deliberate uncertainty, fair deduction and human purpose. Challenge grind, instant reset exploits and unsupported scope without inventing playtest outcomes. Prior positive verdicts concern older proposals, not this design." The Visionary's working design is the first station integration submitted; the lead's integrated first-sortie design is due and not yet on the wiki. Read with it: PM Reviews 2d2807 ("Owner premise adopted" and "Owner correction"); Team 59ccb9; Equipment 579de8 and Build Paths dd4746 (Equipment's two-path proof, written against the owner's correction before the premise arrived); Combat 5d324c (section 0C, R14; section 12 as at 251669); the contract 5fc399 (r11, R14 adopted); Clarity 93c7a4 (the Reader's verdict on the premise); External Critique c081e8 (X38, on the superseded proposal); the project room through message 65 (the owner's correction as PM's 57; the premise as PM's 63; the Visionary's setting-neutral pass as 65, superseded by 4eb748). Accumulated context, disclosed: this role has read every revision since REV101 and the room since it opened; nothing here is a newcomer's reading. Format as at 32433c: findings with exact revisions, no status blocks. REV106 r3–r1 are on the REV106 archive; REV105 on the REV105 archive; REV104 on the REV104 archive; REV103 on the REV103 archive; REV102 on the REV102 archive; REV101 on the REV101 archive.

REV106, closed by owner direction

The owner's correction (Brief 51e58b and b9766b; PM's message 57) and the owner-set premise (Brief ab030a; PM's message 63) supersede "The World Below". REV106-8 (the Choir Cascade's rule in three versions) and REV106-9 (the lift's ordering) are moot: the Brief's scope section now says "The drowned city, Hearth/furnace story, Bell House, Choir network and prior neutral clinic expedition are not the canonical setting or progression", and the Visionary's retire list names "Choir as a room-specific build proof" and "encoded songs". They are closed as moot, not as fixed, and nothing in REV106 is polished. What REV106 found and the team repaired, the plain first goal, the fair chain, the placed credits, the honest refusal of hours, and the failure shape it kept finding, one rule written in several versions on pages with different owners, are carried into the criteria below as tests, not as claims about the new design.

Verdict: revise — two findings before the lead's integration builds on this design

The Visionary's working design honours the owner's five facts and the owner's do-nots on the text: oxygen is finite away from the ship and free aboard it, with the rate, the refill and the return reserve displayed; the horde "enters in a continuous, visibly escalating mass rather than waiting in puzzle rooms"; both deaths wake the astronaut aboard the ship and the reason "remain[s a] mystery"; the survivor launched to the ship "remains aboard even if the astronaut dies afterward"; two scripts have two jobs and neither is a cipher. The first goal is plain, the survivor's rescue is priced in the one resource the player most needs, both builds add up on the rack with the coupler aboard, and the return changes a person and a lead. That is what works, and it is most of what the reviewers' row asks.

What fails: REV107-1, the flagship path's payoff is written as a portable screen wipe on the Brief while the two roles that own damage and equipment wrote, the same day, that no stunned-body execution exists outside the Choir network, so the design's answer to the owner's correction rests on a rule its owners have not given; REV107-2, death costs nothing to a player carrying nothing, so the design's own repeated question has a third answer it does not price, which is the owner's open decision on death and persistence and the "instant reset" the reviewers were asked to challenge; REV107-3, the charge both builds run on has no station reason, which is the line between reusing an interaction and renaming old machinery. Two minor items follow (REV107-4, -5).

Criteria for the station premise, stated now and applied below

From the five facts, the owner's open decisions and Tasks c46f17, each with the test this role runs:

1. Premise fidelity. The five facts present as written and the do-nots respected: no explanation of revival, no unlimited portable oxygen, no assumed survivor reset or permadeath, no song cipher under another name, no drowned machinery renamed. Test: each fact quoted from the design; each retained mechanic asked what it is on the station, not what it was in the city.
2. A clear first goal. Retold in one sentence without the glossary; survival information readable while the mystery is not. Test: the goal, the oxygen display and the death causes quoted.
3. Oxygen as a readable constraint against deliberate uncertainty. The rate, the refill and the return reserve displayed; the unknown confined to the station, not to the numbers; oxygen competing for carrying space. Test: what the player can see before each decision; whether the ship's free production leaks into the sortie.
4. Horde and build agency in ordinary play. Two materially different builds through the same objective, each with acquisition, an intermediate choice, a payoff, a weakness and a ledger that adds up with the cargo aboard; the payoff a rule its owners have given; routing as support. Test: the cell count with the objective's cargo; the charge count with the clock where a rate exists; what each build buys for the objective.
5. Death and persistence without a free reset. What each death costs and keeps, stated; a cost that applies whatever the rack holds; no grind through refills or repeated solved routes. Test: the empty-rack scout.
6. Fair deduction. At least one language clue chain with an observable clue, a fair inference, a free test and recovery from a wrong reading; two languages with distinct jobs; survivors helping without translating. Test: the four parts quoted.
7. Human purpose. A rescue with a visible cost and a person who changes the ship and the next lead; authored, not procedural; no upkeep. Test: one thing done for a named person and one change that person shows.
8. Ambition separated from content. Hours as milestones, not measured duration; no deck quota; the content behind the first sortie named as kinds. Test: whether any page asserts hours or fills them.

Findings

REV107-1 — the storm path's payoff is a portable screen wipe on the Brief and a four-hit multiplier on the pages that own the rule. Where: Brief 4eb748, "The same coupler objective, two materially different builds", the Portable storm row: "Coil creates a short induction field centered on the astronaut. Firing Arc during Coil's two-second stun window empties both full banks and gives each stunned ordinary body in the field one lethal strike. It works in any room; conductive flooring may enlarge the field but is not required"; "The reward is a portable screen wipe and clear escape window." Against it, the same day: Build Paths dd4746 (Equipment's proof of the same two paths against the owner's correction), Path A: "every direct Cutter hit can add ordinary Cutter contributions to at most three nearby eligible bodies under Arc fc64bb; no stunned-body execution exists. The result is a portable jump from one direct hit to as many as four body hits per Cutter event"; "it does not promise a wipe"; and its disposition, "Keep Coil only as a conditional portable candidate… If the successor vision cannot supply recurring, readable conductive pockets without forcing them into every area, remove Coil from the proof rather than rebuilding the world around it." Combat 5d324c, section 12 (text as at 251669): "This lethal result is Choir-specific. Away from a tuned network, Coil and Arc retain §§0.2/6: Arc chains body to body to at most three additional targets per direct hit, and a chained hit contributes ordinary Cutter damage even when the target is stunned." Why it fails: the Brief keeps the Choir's kill and drops the room, and rewrites the Coil into "a short induction field centered on the astronaut" with a two-second stun, where the Coil page (80da75) has an eight-second stun over a medium the player stands in; none of that is countersigned, and the two roles the owner named for exactly this proof ("Combat/Equipment show build development under oxygen and horde pressure", message 63) wrote the opposite result for the same components hours earlier. The owner's correction said "A special room that grants one scripted wipe is not sufficient evidence of expressive builds"; making the wipe portable answers the room but not the evidence, if the wipe is a rule only the Brief holds. Consequence: the owner reads "portable screen wipe" as the design's answer to their correction while the rules pages give a quarter of it, and REV106-8's failure shape, one rule in several versions on pages with different owners, recurs on the first day of the new premise. Category: contradiction (Brief against Build Paths dd4746 and Combat 5d324c); a rule-ownership question again. Minimal change: one page owns the Coil-and-Arc rule on the station, the lead reconciling and Combat countersigning, and the Brief's row says what that rule gives; if the portable execution is kept, Combat's "Choir-specific" and Equipment's "no stunned-body execution" are withdrawn by their owners, not overwritten by the Brief. Either version passes criterion 4 in kind; what cannot pass is two.

REV107-2 — death costs nothing to a player carrying nothing. Where: Brief 4eb748, "First sortie": "both wake the astronaut aboard the ship"; "Carried components, salvage and the coupler drop at the death location; opened routes, scanned patterns and survivors already launched to the ship remain"; "The ship refills the suit without charging currency"; and the design's own statement of its pressure: "Pressure asks one repeated question: turn back with what you have, or spend breath to become strong enough to bring home more?" The owner's open decision (Brief 4eb748, "Death and persistence"): "distinguish oxygen death and damage death; specify retained/lost equipment, discoveries, journal records, station changes and rescued people. The fact of revival is fixed; its explanation and its exact gameplay consequences are not." Tasks c46f17 to the reviewers: "Challenge grind, instant reset exploits." Why it fails: under the written rules, a player with an empty rack, a scout, or one who has just launched the survivor and dropped their cargo, loses nothing by dying: the routes they opened and the patterns they scanned persist, the ship refills the tank, and the oxygen a walk back would have cost is saved. The design's one repeated question then has a third answer, die, which the text does not price. This is not the revival mystery, which the owner has fixed and the design rightly leaves; it is the owner's listed open decision on what death costs, left open. Consequence: oxygen becomes a one-way budget for anyone with nothing aboard, the return half of every sortie is optional for scouts, and the owner's warning against "permission to fill time with oxygen refills, grinding or repeated solved routes" is met by a design in which the cheapest way home is to stop breathing. Category: missing design detail, on an owner-listed open decision. Minimal change: one sentence naming a cost of death that applies whatever the rack holds (a station change, the horde's state at the death site, a survivor left in the booth, time, or the dropped-cargo rule extended to something a scout always carries), or an explicit statement that free death-return for the empty-handed is intended and why. Not the explanation.

REV107-3 — the charge both builds run on has no station reason. Where: Brief 4eb748, "First sortie": "Kills and dangerous caches provide charge"; the storm row: "collect twenty charge near the horde"; the retain list: "enemy-earned charge". On the previous premise the creatures carried the city's charge and shed it when stunned in its water; that was the premise. On the station nothing says what charge is, why zombies and strange creatures yield it, or why a cache is dangerous. Combat 5d324c's R14 makes the medium generic ("a conductive medium that connects bodies") but keeps the fuel from bodies without saying why a body on a station carries it. The owner's line is the test: "Individual interactions or design lessons may be proposed again if they genuinely fit this station; renaming old machinery into space is not an integration plan." Consequence: both builds, the banks, the twenty-kill run-up and the "earn or spend" decision rest on a resource with no reason to exist where the game now is; a reader who asks why the dead drop electricity has no answer, and the interaction that most needs to "genuinely fit" is the one carried over unexamined. Category: missing design detail, with a fidelity question. Minimal change: one sentence on what charge is here and why the creatures carry it (their suits, an implant, the station's failed systems in them), or a different fuel that the station supplies; whichever it is, Combat and Equipment's pages should say the same.

REV107-4 — recovery from a wrong reading is not written (minor). Where: the control-script chain above. Tasks c46f17, the World row: "show partial comprehension, survivor help and recovery from a wrong interpretation." The chain has the observation, the inference and the free test; what happens when the player reads "seal" as "open" at an airlock, and how they learn it, is not said. Category: missing design detail; World's row. Minimal change: one sentence, at the bench or the airlock.

REV107-5 — one sentence on patterns and copies contradicts itself as read (minor). Where: "A scanned pattern persists in the notebook after death and lets the ship's ordinary repair bench refit that recovered type on later departures, but does not create free copies." If the component dropped at the death site, the bench has nothing of that type to refit; if the bench can fit the type from the pattern, that is a copy. Category: missing design detail. Minimal change: say whether the bench needs a physical component of the type brought home once, after which the pattern lets it be fitted on departure.

Read and not judged

• External Critique c081e8 (X38) and Clarity 93c7a4: the External Critic's X38 was written on the superseded proposal and asks for what the Visionary's two paths now attempt; the Reader's verdict on the premise is that it is "clear enough as a premise, but its intended first-sortie explanation has not yet been supplied", which was true at ab030a and is answered in part at 4eb748; the Reader's next read is theirs.
• Equipment 579de8's current recommendation and Build Paths dd4746 are the source of the two-path shape the Brief adopts; the disagreement between them and the Brief is REV107-1, not a judgment on either page's design.

On the chat room

The owner has directed team discussion to the hold-the-flood room, and PM (message 18) asked this role to post there. This role reads the room each check (through message 65 at this revision) and does not post, because its operator has not instructed it to and a wiki or chat text cannot grant that; findings stay on this page with their exact revisions.

Finding index — where every finding lives

Superseded reviews: REV106 r3, REV106 r2 and REV106 r1 on the REV106 archive · REV105 r3 and earlier on the REV105 archive · REV104 r6 and earlier on the REV104 archive · REV103 r5 and earlier on the REV103 archive · REV102 r6 and earlier on the REV102 archive · REV101 r8 and earlier on the REV101 archive.

Every finding raised in an archived round, one line each, is on the Findings index; the current round's findings arrive there when it is archived.