2026-09-10 17:26:48
Anonymous:
Remove review history and align superseded prose with current design rules
hold the flood/save and content state.md ..
@@ 87,9 87,7 @@
## Scope and open decisions
-
**First-pass package estimate:** Systems authoring **8–14 role-hours**, focused review **3–5**, and one response **2–4**; **13–23 role-hours total**. This advances the outline's save/persistence specification row and Design Coverage gap; it is not added again in full to those older envelopes. It excludes UI cue/screen inventories, equipment and oxygen rules, actual rooms/objectives/cast, technical architecture/storage/schema/migrations, implementation, assets, and test execution.
-
-
**Later detailed SMALL state specification:** Systems/technical-design authoring **26–44 role-hours**, review **6–10**, response **3–5**; **35–59 total**. Unique work is the complete transition/commit catalogue, placement and reference matrix, resolved survivor/shift branches, compatibility policy, and concrete authoring-tool requirements. It excludes the same implementation and content production, and must not be added wholesale to overlapping survival, information, trap, station-connection, or Development and Validation Handoff estimates.
+
Remaining detailed work includes the transition and commit catalogue, placement and reference matrix, conditional survivor and shift branches, compatibility policy and authoring-tool requirements. [Production Scope](/Hold%20The%20Flood/Production%20Scope) owns workload estimates.
**Population and reward boundary.** A death shift may select a different finite authored population and begins the new arrangement's transient source/reward state. A **living return** selects no replacement population: defeated creatures stay defeated and resolved stages stay spent for that arrangement, while survivors retain their actual room membership. Temporary combat upgrades nevertheless reset aboard on either kind of return. New arrivals along a cleared route must come from an actual occupied source under [Combat Rules](/Hold%20The%20Flood/Combat%20Rules), not a reset caused by returning or loading. Persistent seals, joins and other completed work remain governed by their owning rules. Quit/load resumes the stored source, stage and reward facts; it creates no award or fresh stage.
