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.
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 | Responsible | Current status | Next estimate, Jerusalem |
|---|---|---|---|
| 41 — Hordes and three builds | Systems | First draft submitted 18:48; revision sent | Today 19:30; range 19:20–19:50 |
| 42 — Pitch and expedition | Design Lead | First draft submitted 18:40; revision received and started | Today 19:30; range 19:20–19:50 |
| 43 — Independent combined review | Reviewer | Completed 18:55; PM disposition recorded | Done; reviewer stopped |
| 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 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.
Forecast
| Milestone | Working target | Plausible window | What must happen |
|---|---|---|---|
| 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 |
| Phase | 9 Sep | 10 Sep | 13–17 Sep | Following weeks |
|---|---|---|---|---|
| Pitch, horde rhythm and builds | Drafts and review done; revise and present | Owner reaction, if still pending | ||
| Rewrite the main reading path | New entry pages drafted | Begin after direction feedback | Revise and integrate | |
| Detailed campaign specification | Parked | Reassess scope | Re-estimate | Resume selected 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.
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.
Start reading with The Game, then Hordes and Builds. These remain working proposals during revision. The Design Plan explains the acceptance criteria; Design Coverage tracks affected areas. The five older unanswered owner choices remain open and do not block this correction.