Blame
|
1 | # Hold The Horde — Progress |
||||||
| 2 | ||||||||
|
3 | **10 September 2026. The next wiki correction is underway.** |
||||||
|
4 | |||||||
|
5 | The first correction produced [The Game](/Hold%20The%20Flood/The%20Game) and [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds): a larger horde experience, three expressive builds, a representative expedition and an explanation of the intended player experience. Those proposals are complete for owner reaction. The broader wiki still needs rewriting. |
||||||
|
6 | |||||||
|
7 | PM had held the next work behind owner feedback. That hold was too broad and has been removed. The owner has now selected the reset rule: temporary combat upgrades end on every return home. Physical equipment and loot are retained. |
||||||
|
8 | |||||||
|
9 | ## Work happening now |
||||||
|
10 | |||||||
|
11 | | Task | Who | Actual status | Next estimate, Jerusalem | |
||||||
| 12 | |---|---|---|---| |
|||||||
| 13 | | 44 — Discovery and the changing station | Systems | Working; receipt and independent priorities confirmed | Draft today 10:50; range 10:40–11:15 | |
|||||||
|
14 | | 45 — People, short rescue and home | Design Lead | Working; automatic delivery succeeded and receiving activity verified | Draft today 10:50; range 10:40–11:15 | |
||||||
| 15 | | 46 — One combined reader and brief review | Reviewer | Criteria prepared; listening for both submissions | After both submitted drafts | |
|||||||
|
16 | | Navigation, dependency preservation and reporting | PM | Active; migration checklist completed and handoffs checked | Alongside these replacements | |
||||||
| 17 | | 38 — Full design readiness | PM | Open | First-pass wiki target 15 September | |
|||||||
| 18 | | 39–40 — Earlier detailed samples | Systems / Lead | Parked and unaccepted | Reassess after direction feedback | |
|||||||
|
19 | |||||||
|
20 | **46 tracked outcomes: 40 preparation outcomes closed, 3 current correction assignments, 1 reopened readiness outcome and 2 parked drafts.** These are writing/review counts, not a percentage of a finished game. Both designers are now working. The reviewer has prepared criteria and is waiting for their submissions. The original Claude sessions recovered; a temporary sign-in refresh interrupted one courier attempt, then the single successful handoff and receiving activity were verified. No further startup step is needed from the owner. |
||||||
|
21 | |||||||
|
22 | The new articles will replace the existing pages at their current URLs. They will explain what the player discovers, how room connections survive shifts, why rescued people matter, and how home supplies relief and a reason to explore again. Essential detailed dependencies will retain clear destinations. |
||||||
|
23 | |||||||
|
24 | ## Estimated deliveries |
||||||
|
25 | |||||||
|
26 | | Milestone | Target | Plausible range / dependency | |
||||||
| 27 | |---|---|---| |
|||||||
|
28 | | Two rewritten reading pages, reviewed | Today 12:15 | 11:30–13:00; Claude roles have resumed and the handoff is complete | |
||||||
|
29 | | Whole readable first-pass wiki | 15 September | 13–17 September; remaining independent work proceeds while specific choices stay open | |
||||||
| 30 | | Detailed campaign design | 17 November | 27 October–15 December; very low confidence until the content scope is re-estimated | |
|||||||
|
31 | |||||||
|
32 | The forecast assumes the three existing roles and PM are available for approximately 6–8 active hours per working day. A missing host is a delivery constraint, not evidence that a task is being worked on. No new permanent agent is currently needed. Game implementation, simulation, playtesting and assets remain separate authorized phases. |
||||||
|
33 | |||||||
|
34 | ## Latest owner decision |
||||||
|
35 | |||||||
|
36 | Temporary combat upgrades earned during an expedition reset whenever the astronaut returns home, alive or revived. The owner selected this on 10 September as the genre-appropriate direction. Physical equipment, components and loot remain retained. The brief and both current reading pages have been updated, and the decision relayed to the team. Exact upgrade effects and pacing remain to be designed. |
||||||
|
37 | |||||||
|
38 | Internal check codes are not progress reports. Future reports describe actual completions, active workers, important changes and estimates in ordinary language. |
||||||
