2026-09-09 18:39:17
Anonymous:
Resume owner-directed correction; replace obsolete status layers with current plan and forecast
hold the flood/progress.md ..
@@ 1,28 1,38 @@
# Hold The Horde — Progress
-
**Paused for owner feedback. Updated 9 September 2026.** All three workers and automatic PM checks remain stopped. Design readiness has been reopened following the owner's review.
+
**Work resumed on 9 September 2026. Updated 18:39 Jerusalem.** The team is correcting the game direction following the owner's review. Automatic PM checks are active.
-
The owner identified three blocking problems:
+
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.
-
1. **Genre and scale:** the described encounters, builds and pacing do not deliver a survivorslike with hordes, spectacle and urgency.
-
2. **Readable design:** the wiki is hard for a human to navigate and understand, with scattered explanations, unexplained references, old discussions and excessive qualifications.
-
3. **Player experience:** the design rarely explains what makes an event fun, exciting or challenging, how pressure and climaxes develop, or what the player is expected to feel and why.
+
## Current work
-
The PM accepts these as failures of the current design and its review standard. Consistency and coverage checks were insufficient grounds for declaring readiness. The earlier closure is a historical preparation milestone; the game direction and wiki now require correction.
+
| Task | Owner | Status | Target, Jerusalem |
+
|---|---|---|---|
+
| 41 — Hordes and three builds | Systems | Working; receipt confirmed | Today 19:15; range 18:55–19:45 |
+
| 42 — Revised pitch and expedition | Design Lead | Working; receipt confirmed | Today 19:15; range 18:55–19:45 |
+
| 43 — Independent review | Reviewer | Criteria saved; ready to review both drafts | Combined critique 20:15, range 19:40–20:45; 45–75 minutes after both submissions |
| 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 |
-
**40 tracked outcomes: 37 preparation-closed, 1 reopened, 2 paused drafts, 0 active.** Earlier completed work remains available for reuse; this count measures documents and reviews, not game quality or percentage complete.
+
**43 tracked design outcomes: 37 preparation-closed, 1 reopened readiness outcome, 2 parked drafts, 3 assigned correction outcomes.** All three roles have confirmed receipt: Systems and Lead are drafting; the Reviewer has saved independent criteria and awaits the drafts. 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.
-
| Outcome | Current state | Next step |
-
|---|---|---|
-
| 38 — [Design readiness](/Hold%20The%20Flood/V1%20Readiness) | Reopened; M2 core and M3 first-pass wiki acceptance withdrawn | Resolve the three owner blockers before declaring readiness again |
-
| 39 — [Opening Mechanism Detail](/Hold%20The%20Flood/Opening%20Mechanism%20Detail) | Paused; submitted draft, unaccepted | Reassess whether its direction is useful after correction |
-
| 40 — [Paired Transfer Discovery Detail](/Hold%20The%20Flood/Paired%20Transfer%20Discovery%20Detail) | Paused; submitted draft, unaccepted | Reassess whether its direction is useful after correction |
+
## Forecast
-
**Proposed next delivery after explicit resumption:** a short revised pitch, one expedition showing pressure and release, three spectacular build examples, and a clear reading structure for the wiki. These are proposals for owner reaction before further detailed specification. No new assignment has been dispatched.
| 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 |
-
**Rough forecast:** one active working day for that correction proposal, then an estimated 2–4 additional working days for a readable first-pass revision after the owner selects the direction. Confidence is low; this estimates a coherent first pass, not exhaustive campaign detail. The team is paused, so no calendar deadline is running. Re-estimate after the proposal establishes how much mechanics/content must change. The previous detailed-campaign target of 10 November (20 October–1 December) is suspended and no longer a reliable baseline following this feedback.
+
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.
-
The owner-confirmed brief remains authoritative. The five earlier unanswered choices remain open. No implementation or playtest is authorized. PM feedback recording does not resume the team.
**What changed:** the earlier 9 September readiness declaration was withdrawn after the owner's three critical objections. 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.
-
Earlier reports and assessments remain in this page's revision history.
+
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.
