2026-09-08 16:27:44
Anonymous:
PM forecast F1.2: actual outline completion and next scoped deliveries
hold the flood/progress.md ..
@@ 1,8 1,8 @@
# Hold The Horde — Progress
-
**Updated 2026-09-08 16:01 Jerusalem (UTC+3).** This is the PM's owner-facing outcome board. The wiki is the shared record. All work remains **design only**.
+
**Updated 2026-09-08 16:27 Jerusalem (UTC+3).** This is the PM's owner-facing outcome board. The wiki is the shared record. All work remains **design only**.
-
**18 tracked design packages: 15 preparation-closed, 3 open.** Outline17 and Player Information18 were explicitly added8 Sep to fill whole-game coverage gaps. Station comparison15 closed363 and first-survivor comparison06 closed368. Shared integration04, outline17 and information/accessibility18 remain open. Of the15 closed packages,6 have owner-selected directions,1 a tentative preference and8 are reviewed proposals/alternatives.
+
**19 tracked design packages: 16 preparation-closed, 3 open.** Whole-game outline17 closed at16:20 today. New package19, Survival and Loadout, was explicitly added under380 to fill a missing core domain. Open: shared integration04 (dependent), Player Information18 (author response379), Survival and Loadout19 (authoring380). Of the16 closed packages,6 have owner-selected directions,1 a tentative preference and9 are reviewed proposals/alternatives.
“Closed” means the bounded written design/review outcome is complete. It does not mean a feature is implemented, every detail approved or fun validated. This board covers the current design batch; it is not a complete campaign or production backlog, and the closed/total ratio is not an overall game-completion percentage. Stable IDs stay fixed; added/reopened work must be recorded explicitly.
@@ 14,13 14,13 @@
|Milestone|Target|Current likely window|Confidence|What will be ready|
|---|---|---|---|---|
-
|M0 — current puzzle/rescue decision pack|Today,8 Sep,16:30|Today16:30–17:00|Medium-high|Reviewed station-connection recommendation and two short first-survivor scenes, with unresolved assumptions exposed|
-
|M1 — whole-game outline and scope bands|Today,8 Sep,17:00 (revised)|Today16:30–17:30|Medium|Draft arrived16:01, ahead of original17:30–18:30 draft window. Focused review and one response remain; original reviewed target18:30/window18:00–20:00 retained in change log.|
+
|M0 — current puzzle/rescue decision pack|Achieved8 Sep15:59|Original target16:30; range16:30–17:00|Actual completion|Both written comparisons reviewed and closed; owner choices remain separate|
+
|M1 — whole-game outline and scope bands|Achieved8 Sep16:20|Original18:30; revised17:00|Actual completion|Draft369, focused review370, response374 and PM integration378 complete; architecture, scope bands and missing-work inventory prepared|
|M2 — coherent core-design baseline|Fri11 Sep|10–14 Sep|Medium-low|One compatible proposed/selected loop: opening, builds, combat, oxygen, death/shift, rescue and home; old conflicting rules replaced and consequential choices dispositioned|
|M3 — complete first-pass game-design wiki, v1|Tue22 Sep|18–29 Sep|Low-medium|Every major gameplay and campaign area has an actual design, a scoped content inventory, dependencies and a usable development handoff outline; major categories are no longer only menus of alternatives|
|M4 — detailed campaign/content specification|Tue10 Nov|20 Oct–1 Dec|Low|The approved finite inventory of regions, rooms, puzzles, clues, encounters, rewards, cast scenes and endings is specified through its state changes and recovery paths|
-
**Will the full wiki be ready today? No.** Today's deliverables are a decision pack and a whole-game outline. **The working target for the first complete design wiki is22 September.** The later detailed-content milestone expands that design into the actual authored campaign. Neither milestone claims that a written plan has proved fun, balance, performance or30/90/100–200hours of play.
+
**Will the full wiki be ready today? No.** Today's decision pack and whole-game outline are prepared; they are not a complete design wiki. **The working target for the first complete design wiki is22 September.** The later detailed-content milestone expands that design into the actual authored campaign. Neither milestone claims that a written plan has proved fun, balance, performance or30/90/100–200hours of play.
For M3, “complete first pass” includes the story's causal chain and ending structure; station layout/shifts/persistence; equipment acquisition and progression; combat/horde/trap families; oxygen/resources; rescue/colony/cast arcs; both language-learning arcs and clue distribution; journal, controls and accessibility; content budget, production constraints and the later validation plan. Numerical tuning can remain explicitly provisional. A major domain marked only “TBD” does not satisfy completion.
|Whole-game outline and scope|Draft / review|Refine|||||
+
|Current decision pack|Done15:59||||||
+
|Whole-game outline and scope|Done16:20|Use for domain design|||||
|Core rules and shared integration||Finish / buffer into14 Sep|||||
|Campaign, puzzles, cast, progression and languages||Start|Develop|Integrate and review|||
|Complete wiki v1|||Draft coverage|Target22 Sep; buffer to29 Sep|||
@@ 41,6 41,8 @@
The critical sequence is core decisions and interfaces → whole-game architecture/content budget → domain designs → cross-domain integration → v1. Content detail proceeds in parallel only where interfaces are stable. Extra writers do not eliminate the PM/review bottleneck.
+
**Next local deliveries:** Player Information author response target17:00 today, range16:45–17:15; PM disposition target17:15, range17:00–17:45. Survival and Loadout draft target17:00, range16:45–17:15; focused review/response target17:30, range17:00–18:00. These are newly scoped packages supporting M2, not replacements for the whole-game milestones.
+
## Extra agents — when and why
**Plan to add two agents tomorrow,9 September**, with bounded briefs prepared today. The current team can finish today's work. We will begin the two specialist streams as the relevant scopes become ready, aiming to have both available by10 September rather than waiting a week.
@@ 68,13 70,14 @@
|---|---|---|
|F1|8 Sep|First forward baseline added at owner's request; prior board had actuals but omitted estimates. M3 target22 Sep; M4 target10 Nov.|
|F1.1|8 Sep16:04|M1 reviewed outline moved from18:00–20:00 to16:30–17:30 because the actual draft arrived16:01 and Reviewer had already fetched it. Review/rework still required. Core, full-wiki and detailed-content dates unchanged.|
+
|F1.2|8 Sep16:20|M0 actual15:59 and M1 actual16:20 recorded. Both prepared ahead of forecast. M2–M4 dates unchanged: the outline is a scaffold, and scope/unit reconciliation is still required before rolling up its partial111–208 role-hour inventory.|
## What changed in this report
-
- Opening A is now the owner's preferred direction: use a reusable part in station machinery to make extraction safer.
-
- The alien-language interaction finished its focused review and correction. It supports learning a useful interaction protocol while keeping the speaker and exact meaning uncertain.
-
- Both new station-wide puzzle concepts have been independently submitted and released. Systems submitted the practical comparison; its focused review is complete, and one author response is now assigned. Reviewer is preauthorised for the first-survivor submission next.
-
- The first-survivor handoff recovered on the original Lead session; its assignment and source reads are verified. No task recreation or owner message forwarding was required. The earlier delivery block is resolved.
+
- The whole-game outline is preparation-closed at16:20, after one focused review and author response. It includes opening through ending/secret layers and finite content bands; later story actions and counts remain proposals.
+
- Player Information draft375 and focused review376 arrived early. Lead is making the consolidated response379, including a coherent short rescue, instrument limits and effort reconciliation.
+
- Systems received380 and is writing the missing survival/loadout contract. Reviewer received the same assignment for independent criteria then the actual submitted draft. Existing hosts and settings are unchanged; no manual forwarding is needed.
+
- A planning discrepancy remains explicit: the outline allows8–16 author hours for a paper UI contract, while the new article estimates8–14 design days for a broader layer. These are not comparable until scope, units and review coverage are separated. Lead379 addresses that; no silent estimate substitution.
## Open and closed outcomes
@@ 98,10 101,9 @@
|14|[Opening expedition: reusable machinery](/Hold%20The%20Flood/First%20Expedition%20Options)|Closed|Option A selected|Prepared Sep8 15:14; selected15:30|Preferred direction recorded; exact starting items/rooms remain proposed|
|16|[Testable alien-language interaction](/Hold%20The%20Flood/Alien%20Utterance%20Discovery)|Closed|Reviewed proposal|Sep8 15:38|Protocol discovery prepared; does not prove request semantics or a god|
-
-
|17|[Whole-game design outline and scope bands](/Hold%20The%20Flood/Whole%20Game%20Outline)|Open — review|New proposed architecture|Sep8 16:01 submission369|Draft369 and focused review370 complete; Systems response371 active. Revised reviewed-window16:30–17:30 today|
-
-
|18|Player information and accessibility|Open — working|New proposed interface contract|Sep8 assignment372|Lead draft17:00–18:00 today; Reviewer preauthorised after independent criteria|
+
|17|[Whole-game design outline and scope bands](/Hold%20The%20Flood/Whole%20Game%20Outline)|Closed|Reviewed planning scaffold|Sep8 16:20 disposition378|Use finite bands and dependencies for domain designs; story/ending/count choices and estimate coverage remain open|
+
|18|[Player information and accessibility](/Hold%20The%20Flood/Player%20Information)|Open — author response|Proposed interface contract|Sep8 draft375/review376|Lead379 response target17:00(range16:45–17:15); PM disposition next|
+
|19|Survival and loadout|Open — working|Provisional resource contract|Sep8 16:23 assignment380|Systems draft17:00(range16:45–17:15); Reviewer criteria then preauthorised review; closeout target17:30(range17:00–18:00)|
|First survivor|Comparison preparation closed368|Owner reaction to Yeva versus Aster|Shared rescue integration; decision pack forecast16:30–17:00 today|
-
|Shared consistency|Old fixed-map claims marked superseded|Use the new connection contract and owner payoff choice|Replace conflicting rules in owning articles|
+
|Whole-station puzzle and first survivor|Both comparisons prepared|Owner reaction to final layout and Yeva/Aster|Shared-rule integration and detailed content|
+
|Player information|Lead379 author response|PM disposition; preserve current proposed resource interfaces|Integrate later survival decisions with bounded information states|
+
|Survival and loadout|Systems380 authoring; Reviewer criteria first|One focused review/response|Core rule integration and first-pass resource scope|
+
|Campaign and production scope|Outline17 prepared|Specialist onboarding9–10Sep; scoping reassessment9Sep18:00|Domain designs and content feasibility|
-
The whole-station contract is the current dependency for shared integration. The first-survivor stream is now running independently after its host recovered. Forward target dates and ranges above now govern planning; they are revised as decisions and actual work change.
+
Shared integration04 depends on the final station contract and decisions. Useful independent information and survival work is active. The owner does not need to forward routine handoffs.
## Decisions for the owner
@@ 132,7 135,7 @@
**Open creative question:** should completing the entire connection puzzle finally stabilise the layout, or should rooms keep moving while every established connection survives? PM recommends stabilisation as a reward for mastery. This is a proposed late payoff, not an answer inferred from the opening choice; the team can continue its comparison while it is pending.
-
The next new creative choice will be the first-survivor scenes. Progression, creature, story and corruption alternatives are prepared for later reactions; the owner is not expected to review the whole wiki at once.
+
The first-survivor choice is also already with the owner: Yeva, the pressure technician preserving ward measurements (PM recommendation), versus Aster, the supply clerk suspicious of the arrival and requesting one reversible door closure. Neither is selected. Progression, creature, story and corruption alternatives are prepared for later reactions; the owner is not expected to review the whole wiki at once.
