2026-09-10 17:27:16
Anonymous:
Remove review history and align superseded prose with current design rules
hold the flood/production scope.md ..
@@ 23,7 23,7 @@
| Person-linked home projects | 5 | 9 / 14 | Voluntary contribution, an observable result, reclaim and personal consequence |
| Special connection challenges | 2 | 4 / 6 | Authored constraint/recovery problems, not the count of ordinary joins |
-
The current SMALL first pass is **4 regions / 24 modules / 40 rooms / 12 objectives / 4 ship assemblies / 5 people / 15 scenes / 12 equipment definitions / 6 ordinary + 3 special roles / 10 encounters including 2 setpieces / 5 mechanism families / 13 major placed mechanisms / 4 language + 4 story chains / 5 home projects / 2 special connection challenges**. These are prepared proposal counts, not an owner-selected game size. Thirteen is not every interactive object: R26/R33 service transformations, the R02/R03 board/rack, ordinary doors and join faces stay owned by their room/interface descriptions rather than becoming extra P-identities. [Campaign Evidence And State Crosswalk](/Hold%20The%20Flood/Campaign%20Evidence%20And%20State%20Crosswalk) closed under PM545 with **26 index entries** across the existing eight chains and fifteen scenes. They are deduplicated index rows, not 26 new objects or single captures; its L/S/A labels are local aliases and do not replace source ownership or established identities.
+
The current SMALL first pass is **4 regions / 24 modules / 40 rooms / 12 objectives / 4 ship assemblies / 5 people / 15 scenes / 12 equipment definitions / 6 ordinary + 3 special roles / 10 encounters including 2 setpieces / 5 mechanism families / 13 major placed mechanisms / 4 language + 4 story chains / 5 home projects / 2 special connection challenges**. These are prepared proposal counts, not an owner-selected game size. Thirteen is not every interactive object: R26/R33 service transformations, the R02/R03 board/rack, ordinary doors and join faces stay owned by their room/interface descriptions rather than becoming extra P-identities. [Campaign Evidence And State Crosswalk](/Hold%20The%20Flood/Campaign%20Evidence%20And%20State%20Crosswalk) contains **26 index entries** across the existing eight chains and fifteen scenes. They are deduplicated index rows, not 26 new objects or single captures; its L/S/A labels are local aliases and do not replace source ownership or established identities.
The 15 SMALL survivor scenes include rescue and home follow-through. Home-project scenes should be assigned within that ledger where possible; if an additional scene is necessary, record the increment instead of silently exceeding fifteen. Branches are variations of a named scene, but each materially different consequence still needs writing and state review.
@@ 57,53 57,37 @@
| Unit | Minimum v1 output | Additional detailed-campaign work |
|---|---|---|
-
| Each of24 reusable modules | Proposed internal geometry, entrance/fixture relationships, available actions and intended discovery/pressure role | Full variants and compatible interface combinations, detailed cue/interaction placement and authored exceptional states |
-
| Each of40 placed rooms | Named identity/module, region and objective links, actual contents/reward, first-visit/revisit purpose, proposed access and recovery constraints | Exact per-instance placement, every selected branch/transient state and concrete consequences across permitted arrangements |
-
| Each of13 major placed mechanisms | First-version geometry, warning, action/stages, reset/rearm and persistence boundary, usable alternative/recovery and linked discovery | Full variant/combined-encounter details, exact thresholds and exhaustive state/recovery paths |
+
| Each of 24 reusable modules | Proposed internal geometry, entrance/fixture relationships, available actions and intended discovery/pressure role | Full variants and compatible interface combinations, detailed cue/interaction placement and authored exceptional states |
+
| Each of 40 placed rooms | Named identity/module, region and objective links, actual contents/reward, first-visit/revisit purpose, proposed access and recovery constraints | Exact per-instance placement, every selected branch/transient state and concrete consequences across permitted arrangements |
+
| Each of 13 major placed mechanisms | First-version geometry, warning, action/stages, reset/rearm and persistence boundary, usable alternative/recovery and linked discovery | Full variant/combined-encounter details, exact thresholds and exhaustive state/recovery paths |
-
A room brief may reference its module and a mechanism brief, but cannot omit its own distinguishing content. V1 retains Design Coverage's thirteen-major-mechanism obligation; the new allowance below makes it explicit. Detailed campaign work extends these accepted briefs rather than charging them again.
+
A room brief may reference its module and a mechanism brief, but cannot omit its own distinguishing content. V1 includes the thirteen major mechanisms. Detailed campaign work extends the first-pass briefs rather than counting their work again.
**Detailed campaign specification:** every approved placed room, mechanism, clue, scene, reward and ending branch has concrete entry/exit, observation, action, interruption, persistence and recovery behaviour. Shared definitions are referenced; instance-specific differences are authored. Precise tuning may still require later evidence. This is larger than a map of twelve objectives.
**Production and validation:** engine architecture, actual tools, runtime content, assets, integration, performance, accessibility testing and real-player evidence. These are a separate, currently unauthorised phase. Documentation completion does not establish a working or enjoyable game.
-
## Current remaining v1 judgment
+
## Workload and forecast status
-
The prior **144–247 role-hour** envelope is retained as a **dated 8 September planning history**. It described work beginning before Regional25 through scope/handoff and combined authoring, review, response and PM integration. It was never a timesheet, and accepted outcomes cannot now be charged again in full. Fast assignment-to-post turnaround records elapsed pipeline time; they do not measure the productive labor needed for every branch, source check or later content implementation.
+
The detailed-campaign allowance below is a planning estimate for the SMALL candidate, not a schedule or logged labor. [Progress](/Hold%20The%20Flood/Progress) owns current work status and forecasts. Milestone dates are suspended during the owner's pause.
-
As of Campaign36 closeout on 9 September, v1 has usable first-pass contracts and finite inventories across all fifteen domains. That is not M3 closure. Verified alignment514 reconciled the global continuity candidate across its named save, connection, rescue, cast, room, encounter, opening, information, death and shifting parents. Verified alignment528 reconciled the accepted mechanical quantities/interfaces across its named catalogue, survival, acquisition, combat, home, room, encounter, build, connection, information, save and continuity parents. Campaign36/PM545 then closed the actual-ID/evidence/state crosswalk for eight chains, fifteen scenes and 26 index entries. Those bounded changes discharge their named contradictions; they do **not** automatically satisfy every broader “M3: reconcile” line in Design Coverage.
+
## Detailed-campaign scope and allowance
-
The earlier **14–24 role-hour** scope37 allowance is retained as a dated 9 September full-cycle estimate for initial authoring, one critique, one response and PM disposition. Initial authoring and critique are now complete; they are not charged again as forward work.
+
Detailed campaign work extends first-pass briefs into exhaustive authored content; it does not count their existing definitions again. A current SMALL candidate needs the following distinct work, with shared observations, scenes and fixtures referenced once:
-
**Dated response snapshot, 9 September:** the following allowance was recorded before scope/handoff37 closed. That response and disposition are now complete; the forward remainder at the start of readiness38 is the **10–18 role-hour coherence allowance**. These are scope judgments, not logged labor or a measured rate.
-
-
| Finite work remaining at that response | Unique work then required | Judgment allowance |
-
|---|---|---:|
-
| Scope/handoff37 response and disposition | This one consolidated response, exact source/diff/readback verification and PM acceptance/integration. | **4–8 role-hours** |
-
| Whole-v1 coherence and bounded repair disposition | Check current links/revisions, stale present-tense claims, owner/proposal labels, interface ownership and cross-article contradictions after 514/528/545; make only evidenced bounded repairs and final M3 disposition. No closed-domain review is repeated. | **10–18** |
-
| **Finite M3 remainder at that response** | Campaign36 is removed because it closed545; accepted initial37 authoring/review is removed; overlap is not charged again. | **14–26 role-hours** |
-
-
This is a forward workload allowance, not a timesheet, a subtraction from chat turnaround or an observed throughput rate. After this response is delivered, the remaining37 share is principally PM verification/disposition within the 4–8 row; the range is not retrospectively reduced by guessing how much productive labor already occurred. Any concrete Coverage residue found by the coherence pass stays inside its 10–18-hour bounded-repair allowance unless the pass demonstrates genuinely new scope.
-
-
The PM's adopted **F1.14** calendar remains the current management forecast: M2 coherent core **11 September (10–14 September)**; complete first-pass M3 wiki **14 September (11–18 September), low confidence**; M4 detailed campaign **10 November (20 October–1 December), low confidence**. This scope analysis does not silently replace those dates. That response-time 14–26-hour allowance, now narrowed to 10–18 for coherence after the scope/handoff closure, is compatible with the M3 range only if the coherence pass finds bounded corrections and PM capacity remains available. A new technical/production specialist on 10 September is conditional on a concrete independent gap and is not counted as available capacity. No extra permanent role or two guaranteed specialists are assumed.
-
-
## M4 detailed-campaign boundary and allowance
-
-
M4 extends accepted first-pass briefs into exhaustive authored content; it does not re-charge their existing definitions. A current SMALL candidate needs the following distinct work, with shared observations, scenes and fixtures referenced once:
-
-
| M4 workstream | Unique deeper work, excluding current first pass | Judgment allowance |
+
| Workstream | Unique deeper work, excluding current first pass | Judgment allowance |
|---|---|---:|
| Rooms, objectives and arrangements | Exact stateful variants for 24 modules/40 rooms/12 objectives, permitted arrangements, traversal, recovery sides and the two special connection challenges. | **90–150 role-hours** |
-
| Encounters and mechanisms | Exact geometry/population/cue/timing/rearm combinations for 10 encounters including 2 setpieces and 13 major mechanisms; fixed services stay in room work. Absorbs the non-v1 remainder of the older traps/region-pressure 33–55 envelope. | **55–95** |
+
| Encounters and mechanisms | Exact geometry/population/cue/timing/rearm combinations for 10 encounters including 2 setpieces and 13 major mechanisms; fixed services stay in room work. | **55–95** |
| Campaign evidence and choice | Full clue distribution, corrections and consequences for 4 language + 4 story chains, deduplicated against objectives and rooms. | **50–85** |
| Cast, rescue and home | Final writing/state variants for 5 people/15 primary scenes/5 home projects; host and branch variants cost work without becoming new primary scenes. | **45–75** |
-
| System detail and information | Exhaustive equipment/survival/build edge cases, exact cue/string/control variants and accessibility equivalence, deduplicated against encounter/room states. This roll-up absorbs the non-v1 remainder of older survival 22–39, equipment 48–78, information 35–59 and conditional survivor-information 8–14 envelopes; survivor dialogue/content remains in Cast. | **65–110** |
-
| Persistence, compatibility and integration | Complete transition/reference/compatibility matrix, version policy, cross-domain review, corrections and PM disposition. Absorbs the non-v1 remainder of the older state 35–59 envelope. | **45–75** |
-
| **M4 SMALL candidate total** | Documentation and authored campaign only; no implementation, assets, recruitment, player sessions or technical validation. | **350–590 role-hours** |
+
| System detail and information | Exhaustive equipment/survival/build edge cases, exact cue/string/control variants and accessibility equivalence, deduplicated against encounter/room states. Survivor dialogue and content remain in Cast. | **65–110** |
+
| Persistence, compatibility and integration | Complete transition/reference/compatibility matrix, version policy, cross-domain review, corrections and PM disposition. | **45–75** |
+
| **SMALL detailed-campaign total** | Documentation and authored campaign only; no implementation, assets, recruitment, player sessions or technical validation. | **350–590 role-hours** |
-
The range is broad because actual branch density, permitted arrangements and final dialogue depth are not yet known; Campaign36 now fixes the index at 26 rows but does not enumerate every M4 occurrence, branch or failure variant. It is not derived from agent typing speed, and it does not prove that the 10 November forecast is achievable. That forecast remains a low-confidence calendar judgment: it requires parallel authoring, bounded revision, no fundamental core-rule reversal and timely owner decisions only where work truly depends on them. Three representative detailed packages—a repeatable mechanism room, a two-language investigation with correction, and a short rescue/home arc—should be authored and independently checked before narrowing this allowance or extrapolating campaign duration.
+
The range is broad because actual branch density, permitted arrangements and final dialogue depth are not yet known. The evidence index has 26 rows but does not enumerate every occurrence, branch or failure variant. Three representative detailed packages—a repeatable mechanism room, a two-language investigation with correction, and a short rescue/home arc—would need to be authored and independently checked before narrowing it or extrapolating campaign duration.
-
The older owning-article envelopes remain dated local planning history and useful decomposition evidence, but the M4 table above is the current cross-domain roll-up after accepted v1 depth is removed. **Do not add either the old full envelopes or their v1 work to 350–590.** When those parents next receive an otherwise necessary M4 edit, Survival And Loadout, Equipment Catalogue/Acquisition and Player Information should label their old ranges as absorbed by “System detail and information”; Traps And Encounter Progression should point to “Encounters and mechanisms”; Save And Content State should point to “Persistence, compatibility and integration.” No parent write is needed solely to spread that note.
+
The table is a cross-domain total after first-pass work is excluded. Shared observations, scenes, fixtures and definitions are counted once; separate article estimates must not be added to the **350–590 role-hours**.
The owner's **30/90/100–200-hour** ambitions remain unproven. SMALL is a costed candidate for estimating authored work, not an owner-selected downgrade or a demonstrated playtime band. TARGET and STRETCH remain alternatives whose branch interactions require their own estimate rather than multiplication from SMALL.
@@ 128,4 112,4 @@
These are separate alternatives; adopting both requires evaluating their combined loss of variety. Neither adds oxygen grind, repeated death requirements, loot loss or a longer escort to compensate for fewer authored units. Preserve all owner pillars first, and judge the actual retained experiences before adopting a cut. Larger counts remain plausible if later authoring and player evidence support them.
-
**Reopening conditions:** a complete ledger reveals missing scenes/branches; a core rule changes many interfaces; owner scope or ending choices change; representative detailed packages exceed allowances; staffing fails to materialise; or later authorised evidence shows repetition, poor comprehension or unaffordable runtime/content work. Revise the forecast and name the affected outcome instead of silently moving the date.
+
**Reopening conditions:** a complete ledger reveals missing scenes/branches; a core rule changes many interfaces; owner scope or ending choices change; representative detailed packages exceed allowances; staffing fails to materialise; or later authorised evidence shows repetition, poor comprehension or unaffordable runtime/content work. Any revised scope or forecast belongs in [Progress](/Hold%20The%20Flood/Progress).
