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.
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.
Current work
| Task | Owner | Status | Target, Jerusalem |
|---|---|---|---|
| 41 — Hordes and three builds | Systems | Submitted at 18:48; PM read | In combined review |
| 42 — Revised pitch and expedition | 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 |
| 38 — Design readiness | PM | Reopened; awaits correction and owner reaction | First-pass revision target 15 September |
| 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 |
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.
Forecast
| Milestone | Working target | Plausible window | Dependency |
|---|---|---|---|
| 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.
| Phase | 9 Sep | 10 Sep | 13–17 Sep | Following weeks |
|---|---|---|---|---|
| Pitch, horde rhythm and build examples | Draft | Review / owner reaction | ||
| Rewrite the main reading path | Structure | Begin after direction | Revise / integrate | |
| Detailed campaign specification | Parked | Parked | Re-estimate | Resume selected detail work |
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.
Read the Design Plan for the correction's acceptance criteria and Design Coverage for the affected areas. Design readiness remains open. The five earlier unanswered owner choices remain unresolved; they do not prevent this correction work.