Blame
|
1 | # Hold The Horde — Progress |
||||||
| 2 | ||||||||
|
3 | **10 September 2026. Discovery and home rewrites are complete; combat and build rules are being corrected next. All times below are Jerusalem.** |
||||||
|
4 | |||||||
|
5 | We are addressing three owner concerns: convincing survivorslike hordes and spectacular builds, a readable wiki, and a clear account of the player's fun, excitement, challenge and emotional experience. |
||||||
| 6 | ||||||||
| 7 | ## Completed this morning |
|||||||
| 8 | ||||||||
| 9 | - **Two existing articles rewritten and reviewed:** [Discovery in a changing station](/Hold%20The%20Flood/Connecting%20The%20Station) and [Home and the people you bring back](/Hold%20The%20Flood/Home%20And%20Colony%20Loop). |
|||||||
| 10 | - **One independent critique and one consolidated author response completed.** PM checked the actual sources and corrected factual overclaims. The pair closed at 10:48, ahead of the revised 11:15 estimate. |
|||||||
| 11 | - **Eight reference pages repaired** so the new explanations link to the right definitions. This was scoped repair, not a full rewrite of those references. |
|||||||
| 12 | - **Four-page reading route published:** [start with the game](/Hold%20The%20Flood). |
|||||||
| 13 | ||||||||
| 14 | Your decision is recorded: temporary combat upgrades reset on every return home, alive or revived. Physical equipment, components and loot are retained. |
|||||||
|
15 | |||||||
|
16 | ## Work happening now |
||||||
|
17 | |||||||
|
18 | | Task | Responsible | Status and concrete result | Next estimate | |
||||||
|
19 | |---|---|---|---| |
||||||
|
20 | | 47 — Spectacular builds and expedition growth | Systems | Active: replace Build Rules and repair acquisition/controller rules, including multiple weapons, paused link editing and the selected reset | Draft within this batch's 12:00–13:00 window | |
||||||
| 21 | | 48 — Ordinary hordes and encounter pressure | Design Lead | Working: replace Combat Rules and revise the roster and all ten encounter placements | Drafts 12:15–12:45 | |
|||||||
| 22 | | 49 — One combined review | Reviewer | Preparing independent criteria; review follows both submitted drafts | Included in the 14:00 reviewed-batch target | |
|||||||
| 23 | | Integration, source checks and owner updates | PM | Active; six existing articles assigned with separate writers | Alongside drafts and review | |
|||||||
|
24 | | 38 — Full design readiness | PM | Reopened after owner feedback | First-pass wiki target 15 September | |
||||||
|
25 | | 39–40 — Earlier detailed samples | Systems / Design Lead | Parked and unaccepted | Reassess after correction | |
||||||
|
26 | |||||||
|
27 | **49 tracked outcomes: 43 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. |
||||||
|
28 | |||||||
|
29 | The next work repairs real contradictions: old encounter populations are only 1–5 creatures, and old rules still impose a single ordinary-weapon limit and exposed rewiring. The newer proposal calls for massed ordinary combat, expressive combinations and link changes during journal pause. Particular populations, growth effects and editing details remain proposals; the brief is the source of owner-selected rules. |
||||||
|
30 | |||||||
|
31 | Both original Claude tasks are available, automatic handoffs succeeded, and receiving activity was checked. The owner does not need to forward routine messages. No extra permanent agent is needed for this batch. |
||||||
|
32 | |||||||
|
33 | ## Estimated deliveries |
||||||
|
34 | |||||||
|
35 | | Milestone | Target | Plausible range | |
||||||
|
36 | |---|---|---| |
||||||
|
37 | | Combat/build drafts and scoped reference repairs | Today 12:30 | 12:00–13:00 | |
||||||
| 38 | | Reviewed, integrated combat/build batch | Today 14:00 | 13:00–15:00 | |
|||||||
|
39 | | Whole readable first-pass wiki | 15 September | 13–17 September | |
||||||
| 40 | | Detailed campaign design | 17 November | 27 October–15 December | |
|||||||
|
41 | |||||||
|
42 | The next batch's initial 13:00 reviewed target moved to 14:00 after the Lead inspected about 115 KB of source and identified the space and population checks needed for ten placements. The broader dates are unchanged. Confidence is moderate for the next batch, low for the first-pass wiki and very low for detailed campaign work until scope is re-estimated. |
||||||
|
43 | |||||||
|
44 | Dates assume the three existing roles and PM are available approximately 6–8 active hours per working day. A first-pass wiki means a coherent, readable proposed design with open choices clearly identified. It does not establish fun, balance or campaign duration. Game implementation, simulation, playtesting and assets require their separate authorization. Unanswered creative choices block only the work that depends on them. |
||||||