2026-09-09 19:06:07
Anonymous:
Record completed critique, focused response and earlier owner delivery estimate
hold the flood/progress.md ..
@@ 1,38 1,40 @@
# Hold The Horde — Progress
-
**Work resumed on 9 September 2026. Updated 18:53 Jerusalem.** The team is correcting the game direction following the owner's review. Automatic PM checks are active.
+
**9 September 2026, 19:09 Jerusalem.** Both first drafts and their combined review are complete. The authors have been sent one focused revision pass. The next delivery is a short, corrected proposal for the owner to react to.
-
The next owner delivery is a revised pitch, an expedition with convincing horde pressure and discovery, and three spectacular build examples. It must address all three blockers: survivorslike scale and urgency, human-readable explanations, and concrete reasons for fun, challenge and emotional payoff.
+
We are addressing three failures identified by the owner: insufficient survivorslike scale and urgency, a wiki difficult to read, and too little attention to the player's fun, pressure and emotional payoff. Earlier readiness acceptance remains withdrawn.
## Current work
-
| Task | Owner | Status | Target, Jerusalem |
+
| Task | Responsible | Current status | Next estimate, Jerusalem |
|---|---|---|---|
-
| 41 — [Hordes and three builds](/Hold%20The%20Flood/Hordes%20and%20Builds) | Systems | Submitted at 18:48; PM read | In combined review |
-
| 42 — [Revised pitch and expedition](/Hold%20The%20Flood/The%20Game) | Design Lead | Submitted at 18:40; PM read, corrections needed | First draft delivered early; response follows combined review |
-
| 43 — Independent review | Reviewer | Reviewing both drafts; start confirmed at 18:52 | Today 19:50; range 19:35–20:10 |
| 39–40 — Earlier mechanism/discovery details | Systems / Lead | Parked, unaccepted drafts | Reassess after the new direction |
-
| Clear wiki navigation and current reports | PM | In progress; reading map prepared | Alongside the corrected proposal |
+
| 41 — [Hordes and three builds](/Hold%20The%20Flood/Hordes%20and%20Builds) | Systems | First draft submitted 18:48; revision sent | Today 19:30; range 19:20–19:50 |
+
| 42 — [Pitch and expedition](/Hold%20The%20Flood/The%20Game) | Design Lead | First draft submitted 18:40; revision received and started | Today 19:30; range 19:20–19:50 |
| Corrected proposal for owner reaction | PM | Awaiting the two revisions, then final source check | Tonight 20:15; range 19:45–21:00 |
+
| 38 — Design readiness | PM | Reopened; awaits correction and owner reaction | First-pass wiki target 15 September |
+
| 39–40 — Earlier mechanism and discovery details | Systems / Lead | Parked, unaccepted drafts | Reassess after direction feedback |
-
**43 tracked design outcomes: 37 preparation-closed, 1 reopened readiness outcome, 2 parked drafts, 3 assigned correction outcomes.** All three roles have confirmed receipt: Both authors have submitted and stopped; the Reviewer is examining the two drafts against independently saved criteria. Both proposals remain unaccepted. These counts describe writing and review outcomes, not the percentage of the game complete. The temporary wiki assistant's reading map is PM support, not another design outcome or permanent role.
+
**43 tracked outcomes: 38 preparation outcomes closed, 2 correction drafts in revision, 1 reopened readiness outcome and 2 parked drafts.** The two drafts have received one combined critique; neither is accepted yet. The review is complete as an assignment, but PM rejected several of its claims after checking the actual text and brief. These are document and review counts, not a game completion percentage.
+
+
The revision preserves the strongest additions: massed ordinary combat, three visually different builds, rising power during an expedition, and discoveries that reveal much larger spaces. It clarifies living return versus death, short rescue completion, the relationship between regular hordes and optional larger events, and the benefits and costs of temporary upgrades.
| Milestone | Working target | Plausible window | What must happen |
|---|---|---|---|
-
| Corrected proposal for owner reaction | 10 September, 18:00 | This evening–10 September evening | Both drafts, one focused critique and a bounded response |
-
| Readable, coherent first-pass design wiki | 15 September | 13–17 September | Owner reaction to the direction; approximately 2–4 further working days of revision |
-
| Detailed campaign design | 17 November | 27 October–15 December | Selected direction and a fresh estimate of the resulting content/detail work |
-
-
Confidence is low for the first two targets and very low for detailed campaign design. Dates assume the existing three roles and PM remain available, approximately 6–8 active hours per working day, and consequential owner feedback within a working day. An earlier useful proposal will be delivered immediately. These are design estimates; development has a separate authorization and schedule.
+
| Corrected proposal for owner reaction | 9 September, 20:15 | Tonight 19:45–21:00 | Both author responses and PM verification |
+
| Readable, coherent first-pass design wiki | 15 September | 13–17 September | Owner reaction, then approximately 2–4 further working days of rewriting and integration |
+
| Detailed campaign design | 17 November | 27 October–15 December | Selected direction and fresh estimates of content and detail work |
**Forecast change:** the next proposal has moved forward from 10 September at 18:00 to tonight at 20:15. Both drafts arrived before their 19:15 target, and the review finished at 18:55. The remaining response is bounded. This earlier target remains an estimate, with delivery as soon as a useful packet is ready.
-
**What changed:** the earlier 9 September readiness declaration was withdrawn after the owner's three critical objections. Both first drafts arrived ahead of the 19:15 target; the review target has moved from20:15 to19:50. The old 10 November detailed-design target has moved to a provisional 17 November and its range widened to allow for mechanical and content rework. This extra allowance is a planning judgment, not measured remaining effort. Previous forecasts remain in page history and the PM forecast checkpoint.
+
Confidence is low for the wiki dates and very low for the detailed campaign. Dates assume the current three roles and PM remain available for approximately 6–8 active hours per working day, and consequential owner feedback within a working day. No additional permanent agent is currently needed. Development and playtesting have their own authorization and schedule.
-
Read the [Design Plan](/Hold%20The%20Flood/Design%20Plan) for the correction's acceptance criteria and [Design Coverage](/Hold%20The%20Flood/Design%20Coverage) for the affected areas. [Design readiness](/Hold%20The%20Flood/V1%20Readiness) remains open. The five earlier unanswered owner choices remain unresolved; they do not prevent this correction work.
+
Start reading with [The Game](/Hold%20The%20Flood/The%20Game), then [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds). These remain working proposals during revision. The [Design Plan](/Hold%20The%20Flood/Design%20Plan) explains the acceptance criteria; [Design Coverage](/Hold%20The%20Flood/Design%20Coverage) tracks affected areas. The five older unanswered owner choices remain open and do not block this correction.
