Blame
|
1 | # Hold The Horde — Progress |
||||||
| 2 | ||||||||
|
3 | Updated **15 September**. The owner has chosen **fresh hordes each expedition** and **regular growth through fighting, with larger transformations**. Permanent changes and carried property remain; temporary combat power resets whenever you return home. |
||||||
|
4 | |||||||
|
5 | ## Ready to read |
||||||
|
6 | |||||||
|
7 | **Sixteen proposal or editorial packages have been completed today.** The latest finished at **17:18 Jerusalem time**: [two trips with the same equipment and different earned upgrades](/Hold%20The%20Flood/Upgrade%20Choices), including a useful hybrid and a reach-versus-contacts trade. Systems has started a scene about recognizing one former patient within an existing horde and bringing that knowledge home. The separate short-rescue choice remains open. |
||||||
|
8 | |||||||
|
9 | Start with [The Game](/Hold%20The%20Flood/The%20Game), continue through [three expeditions into the observation ward](/Hold%20The%20Flood/Expedition%20Proposal), then [Coming Home](/Hold%20The%20Flood/Coming%20Home) and [Discovery in a Changing Station](/Hold%20The%20Flood/Connecting%20The%20Station). For combat, follow [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds) into [Three Ways to Break a Horde](/Hold%20The%20Flood/Build%20Comparison). |
||||||
|
10 | |||||||
|
11 | | Completed package | Actual time today | What changed | |
||||||
| 12 | |---|---|---| |
|||||||
| 13 | | 59–61 — Builds and three expeditions | 12:08 | Different movement and payoff proposals; successive trips pursue different discoveries | |
|||||||
| 14 | | 56–58 — Hospital story and survival | 12:32 | Two possible core mysteries; comparable loadouts with a visible cost for the heavier kit | |
|||||||
| 15 | | 62–63 — Regular growth and renewed combat | 12:45 | An ordinary improvement before a major breakthrough, with crowds and discovery quiet placed along an existing route | |
|||||||
| 16 | | 64–65 — Combat after permanent seals | 13:26 | A second route state retains the seals and shortcut while enemies arrive from a distant open source; room and encounter references agree | |
|||||||
| 17 | | 66–67 — Six main reading pages | 13:26 | Player scenes lead; unfamiliar terms are explained; onward links work; obsolete clearing and growth claims are removed | |
|||||||
|
18 | | 68 — Moving scan and bridge | 14:01 | A rising fight through Cable Junction leads to a local optical discovery and usable bridge; living returns preserve the shortcut, while changed alignments have a visible rescan route | |
||||||
|
19 | | 69 — Short rescue and death comparison | 14:20 | A person’s records, a short horde crossing and a homecoming; two unselected failure approaches with explicit protection and retry costs | |
||||||
|
20 | | 70 — Completing the station | 14:36 | The final join secures the last piece of a dependable home; an alternative adds optional departure with the whole station, with its production and story costs explicit | |
||||||
|
21 | | 71 — Campaign scope comparison | 14:56 | A 40-room reference versus 36 denser rooms, with named losses and retained work; current mechanism counts aligned and old hour allowances clearly qualified | |
||||||
|
22 | | 72 — Language journal | 15:06 | [Capture, compare and test a reading](/Hold%20The%20Flood/Language%20And%20Journal), with both language examples and the value of old records explained in place | |
||||||
|
23 | | 73 — Whole campaign | 15:26 | [The campaign from docking to deepest discoveries](/Hold%20The%20Flood/Whole%20Game%20Outline), with the horde/build/bridge climax, human consequences and open endings explained | |
||||||
|
24 | | 74 — People and short rescues | 15:44 | [Five people and their fifteen scenes](/Hold%20The%20Flood/Cast%20And%20Short%20Rescue%20Map), with their wishes, disagreements and later changes of belief explained before the shared rules | |
||||||
|
25 | | 75 — Equipment and combinations | 16:05 | [Twelve equipment parts](/Hold%20The%20Flood/Equipment%20Catalogue), introduced through visible behavior and a working build; readiness and installed-part explanations corrected | |
||||||
|
26 | | 76 — Receiver Vault expedition | 16:30 | [Turn the shelter, break a firing lane and investigate the iris](/Hold%20The%20Flood/Receiver%20Vault%20Expedition); proposed nearer arrival and existing longer route preserve different power choices | |
||||||
|
27 | | 77 — Enemy guide | 16:46 | [Nine creatures and two horde setpieces](/Hold%20The%20Flood/Combat%20And%20Enemy%20Roster), explained through visible warnings, pressure and responses; rescue and carrying examples corrected | |
||||||
|
28 | | 78 — Two trips, two different builds | 17:18 | [The same rig takes different earned paths](/Hold%20The%20Flood/Upgrade%20Choices); real declined alternatives, a hybrid, a new reach trade and the cost of a small offer pool | |
||||||
|
29 | |||||||
|
30 | Each package received one focused critique, one response and PM checks. These are completed design proposals, not tested gameplay. The new Ricochet and Gravity controls remain proposed alternatives to the current detailed equipment rules. The two renewed-route examples do not yet cover every shifted layout or combination of permanent seals. |
||||||
|
31 | |||||||
|
32 | ## Working now |
||||||
|
33 | |||||||
|
34 | | Outcome | Owner and current state | Next delivery, Jerusalem time | |
||||||
| 35 | |---|---|---| |
|||||||
|
36 | | 79 — A person in the crowd | Systems is working; independent criteria saved and reviewer ready | Draft **18:50**, range **18:20–19:20**; reviewed proposal **20:00**, range **19:15–20:45** | |
||||||
|
37 | | 38 — Full-design readiness, still reopened | Outside-edit preservation audit completed; eleven factual/reference corrections published. Supporting readability and broader experience coverage remain | Readiness reassessment with the coherent wiki pass, target **23 September**, range **21–28 September** | |
||||||
|
38 | |||||||
|
39 | Read the scene in [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds), with placement in [Moving Scan Expedition](/Hold%20The%20Flood/Moving%20Scan%20Expedition). Its added rail, viewing bay, bridge and receiver make a fourteenth proposed major mechanism; physical fit and fun remain untested. The new Receiver Vault proposal tackles a different risk: a later expedition must deliver growing power and a horde climax before its quiet discovery. It uses the existing vault rooms, enemies and machinery; the new reward opportunity remains a proposal. Earlier rescue and station-completion comparisons are ready for owner reaction. |
||||||
|
40 | |||||||
|
41 | The tracker contains **79 outcomes: 75 preparation outcomes closed, 1 current design outcome, 1 readiness assessment reopened and 2 parked**. The completed preservation audit and its corrections belong within outcome 38; they do not close overall readiness. These counts are not a percentage of the finished game. Outcomes 39–40 remain parked and unaccepted pending the core corrections. |
||||||
|
42 | |||||||
|
43 | The original Claude Reviewer received the earlier assignment automatically but stopped at a monthly spend limit at 13:03. Temporary GPT support completed that review. The Lead was absent from the same directory check; availability will be checked again before a future handoff. No new permanent agent or manual message forwarding is needed for the current assignments. |
||||||
|
44 | |||||||
|
45 | ## Delivery forecast |
||||||
|
46 | |||||||
|
47 | Forecast **F2.27**, updated 15 September. Dates assume work continues today and about five further active working days for the first full pass. |
||||||
|
48 | |||||||
|
49 | | Milestone | Target | Plausible range | Completion means | |
||||||
|
50 | |---|---|---|---| |
||||||
|
51 | | Reviewed sealed-source expedition | **Completed today 13:26** | Earlier than 15:00 target | Proposal, critique, response and integration into its owning references | |
||||||
| 52 | | Clear six-page reading path | **Completed today 13:26** | Earlier than 16:00 target | Main journey and combat branch revised and checked against current rules | |
|||||||
|
53 | | Moving-scan proposal | **Delivered 13:39** | Earlier than 14:15 target | Concrete location, rising fight, build climax, discovery and next trip | |
||||||
| 54 | | Reviewed moving-scan proposal | **Completed 14:01** | Earlier than 15:30 target | One critique, one response and verified integration across six articles | |
|||||||
| 55 | | Outside-edit preservation audit | **Completed 13:47; follow-up corrections 13:52** | Earlier than 14:15 report target | All 58 captured changes inspected with provenance; identified factual/preservation defects corrected | |
|||||||
|
56 | | Short-rescue proposal | **Delivered 14:03** | Earlier than 14:30 target | One personal rescue scene and two comparable failure approaches | |
||||||
|
57 | | Reviewed short-rescue proposal | **Completed 14:20** | Earlier than 15:15 target | One critique and response; owner comparison published, shared rules await selection | |
||||||
|
58 | | Station-completion comparison | **Completed 14:36** | Earlier than 16:00 target | Two reviewed consequences of the last connection, with the next home visit and expedition | |
||||||
|
59 | | Costed campaign comparison | **Completed 14:56** | Earlier than 17:00 target | Named retained, moved and removed experiences; current counts and historical allowance distinguished | |
||||||
|
60 | | Readable language journal | **Completed 15:06** | Earlier than 16:15 target | Existing journal explanation leads with player use and discovery, with current rules preserved through review | |
||||||
|
61 | | Readable campaign overview | **Completed 15:26** | Earlier than 16:00 target | Opening through deeper and optional play shows horde growth, discoveries and people, with current proposals distinguished | |
||||||
|
62 | | Readable cast and rescue map | **Completed 15:44** | Earlier than 17:00 target | Five people and fifteen scenes lead with their choices and changing relationships; current waiting places and unresolved rescue choices remain clear | |
||||||
|
63 | | Readable equipment reference | **Completed 16:05** | Earlier than revised 16:30 target | A reader can picture the twelve parts and their combinations, find actual costs and distinguish current mechanisms from proposed alternatives | |
||||||
|
64 | | Reviewed Receiver Vault expedition | **Completed 16:30** | Earlier than revised 17:15 target | A complete later expedition, ordinary growth and a major transformation used during the fight, a meaningful climax and a discovery that changes the next trip; one critique and response | |
||||||
|
65 | | Readable enemy guide | **Completed 16:46** | Earlier than revised 17:15 target | The nine creatures, their horde roles and two setpieces are explained through what the player sees, chooses and overcomes, with actual behaviors retained through review | |
||||||
|
66 | | Divergent upgrade choices | **Completed 17:18** | Earlier than revised 18:00 target | The same equipment supports two different earned growth paths, a useful hybrid and understandable choices with costs; one critique and response | |
||||||
| 67 | | A person in the crowd | Today **18:50** draft; **20:00** reviewed | Draft **18:20–19:20**; reviewed **19:15–20:45** | One existing ward encounter becomes a personal discovery, with an optional home response, a simpler record-only alternative and explicit renewal/content costs | |
|||||||
|
68 | | Coherent revised design wiki | **23 September** | **21–28 September** | Readable core and supporting rules aligned; consequential choices explicit | |
||||||
| 69 | | Full detailed campaign design | **24 November** | **3 November–22 December** | Proposed progression, content, mysteries, ending paths and production scope developed across the campaign | |
|||||||
|
70 | |||||||
|
71 | The patient-scene estimate has moderate-to-low confidence because preserving one identity across renewed expeditions may require a simpler treatment. Other near-term estimates have moderate confidence. The full-wiki estimate has low confidence. The campaign date has very low confidence and remains a planning allowance pending a fresh content estimate. None promises development, validated fun or the desired number of playable hours; those require a separately authorized phase. |
||||||
|
72 | |||||||
|
73 | The pre-pause targets were 15 September for the readable wiki and 17 November for detailed campaign design. Five paused calendar days and the outside review's core-loop findings moved those dates. F2.27 records the upgrade comparison completed at 17:18 after one critique and response, ahead of its revised 18:00 target. The next assignment began at 17:21 and addresses the human meaning of an existing horde encounter. Its allowance is 60–120 minutes for a draft plus review, response and integration; a record-only comparison is available if the recognition scene demands too much new state. The overall dates remain unchanged because broader experience coverage, supporting clarity and consequential creative choices still need work. Earlier estimates and reasons remain in revision history and the forecast checkpoint. |
||||||
|
74 | |||||||
|
75 | ## What still needs work |
||||||
|
76 | |||||||
|
77 | - Broader expeditions must sustain fresh combat, meaningful growth and different discoveries around persistent changes. |
||||||
| 78 | - Build combinations need distinct decisions and room for surprising interactions. The new alternatives still need selection and detailed integration. |
|||||||
| 79 | - Rooms, people, languages and story consequences need concrete scenes with emotional and discovery payoffs. |
|||||||
|
80 | - Supporting pages need the same clarity as the entry path. The captured outside-edit bundle has been audited and its identified factual defects corrected; that preservation check does not establish that every page is easy for a human to read. |
||||||
|
81 | - Full readiness requires a coherent player journey and honest scope, beyond internally consistent tables. |
||||||
|
82 | |||||||
|
83 | ## Owner choices |
||||||
|
84 | |||||||
|
85 | The two immediate combat questions are answered in the [Owner Brief](/Hold%20The%20Flood/Brief). The current concrete choice is in [Rescue Under Pressure](/Hold%20The%20Flood/Rescue%20Under%20Pressure): if the astronaut dies after Yeva starts crossing the prepared short route, does she finish and reach the ship, or take shelter and require a new attempt after the shift? PM recommends finishing; the stronger failure/retry case and both safety exceptions are explained. The owner has been asked directly; no answer is inferred. The first survivor and wider survivor mortality remain open. |
||||||
|
86 | |||||||
|
87 | The earlier build-priority question also remains: which direction to deepen first. It does not discard the others or approve every proposed rule. |
||||||
| 88 | ||||||||
|
89 | [Completing The Station](/Hold%20The%20Flood/Completing%20The%20Station) is ready to compare: finish securing a dependable home, or add an optional departure carrying the entire place. This is prepared for a subsequent owner choice; the rescue question above remains the current question. The [campaign scope comparison](/Hold%20The%20Flood/Campaign%20Scope%20Choices) is reviewed and ready for subsequent reaction; neither size is selected, and existing story alternatives remain available for reaction. [Open Decisions](/Hold%20The%20Flood/Open%20Decisions) is the wider issue index; its recommendations remain proposals. Its fourteen categories are not fourteen answers needed before work can continue. |
||||||
