2026-09-09 19:15:21
Anonymous:
Record the corrected proposal ready for owner reaction and remaining wiki work
hold the flood/progress.md ..
@@ 1,40 1,46 @@
# Hold The Horde — Progress
-
**9 September 2026, 19:06 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.
+
**9 September 2026, 19:15 Jerusalem. The corrected proposal is ready for owner reaction.**
-
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.
+
Read [The Game](/Hold%20The%20Flood/The%20Game) first, then [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds). Together they show a representative expedition, ordinary crowd pressure, three expressive builds, discovery payoffs and the player's intended emotional experience.
-
## Current work
+
## Completed and open work
-
| Task | Responsible | Current status | Next estimate, Jerusalem |
-
|---|---|---|---|
-
| 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 |
+
| Task | Result | Actual completion, Jerusalem |
+
|---|---|---|
+
| 41 — Hordes and three builds | Revised proposal checked and included | Author response 19:07; PM closeout 19:13 |
+
| 42 — Pitch and expedition | Revised and simplified; controls, rescue and shifts clarified | Author response 19:09; PM closeout 19:13 |
+
| 43 — Independent combined review | One critique completed; PM checked and resolved its findings | 18:55 |
+
| Corrected proposal | Ready for owner reaction | 19:13, ahead of the 20:15 target |
+
| 38 — Full design readiness | Open; broader wiki correction still required | Target 15 September |
+
| 39–40 — Earlier detailed samples | Parked and unaccepted | Reassess after direction feedback |
+
+
**43 tracked outcomes: 40 preparation outcomes closed, 1 reopened readiness outcome and 2 parked drafts.** This counts writing and review work, not the proportion of a finished game. Both designers and the reviewer have completed this bounded correction and stopped. The next dependency is the owner's reaction before expanding the selected direction through the wiki. No routine message forwarding or new permanent agent is needed.
-
**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.
+
## What changed
-
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.
+
- Ordinary exploration now includes substantial local hordes; larger events can also be triggered through discovery and machinery.
+
- Three concrete builds create chain storms, multiplying ricochets and a gathering gravity burst.
+
- Temporary combat upgrades propose a rise in power within each expedition. Their reset rule is a current owner question; physical equipment and loot are retained.
+
- The expedition explains player choices, pressure, spectacle, curiosity and relief, with concrete ways each intended experience could fall flat.
+
- The main reading pages and navigation are clearer. The broader wiki rewrite is still ahead.
-
## Forecast
+
The first proposal after feedback is complete. Its fun, balance and performance remain design hypotheses; the earlier full-wiki readiness acceptance stays withdrawn.
-
| Milestone | Working target | Plausible window | What must happen |
+
## Forward estimates
+
+
| Milestone | Working target | Plausible window | Main dependency |
|---|---|---|---|
-
| 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 |
+
| Owner reaction and next rewrite assignments | Next working day after feedback arrives | Same day–next working day | Direction and temporary-upgrade choice |
+
| Readable, coherent first-pass design wiki | 15 September | 13–17 September | Approximately 2–4 further working days after direction feedback |
+
| Detailed campaign design | 17 November | 27 October–15 December | Selected direction and a fresh estimate of content 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.
-
-
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.
+
Confidence is low for the first-pass wiki and very low for the detailed campaign. These estimates assume the existing three roles and PM are available for approximately 6–8 active hours per working day and consequential owner feedback within a working day. Development and playtesting require separate authorization and scheduling. The early completion of this small correction does not yet justify pulling the whole campaign schedule forward.
-
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.
+
See the [Design Plan](/Hold%20The%20Flood/Design%20Plan) for acceptance criteria and [Design Coverage](/Hold%20The%20Flood/Design%20Coverage) for the remaining rewrite areas. The five earlier unanswered owner choices remain open; they were not decided through the illustrative expedition.
