2026-09-15 11:53:48
Anonymous:
Align resumed design work and confirmed expedition choices
hold the flood/progress.md ..
@@ 1,86 1,59 @@
# Hold The Horde — Progress
-
**Paused by the owner — 10 September, 15:13 Jerusalem.** Work and automatic checks are paused to conserve GPT tokens. We will resume only when the owner asks. Current delivery estimates are suspended and will be updated then.
+
Work resumed on **15 September**. The immediate goal is a game proposal that delivers fresh horde combat, an exciting rise in power, surprising discoveries and builds that play differently on successive expeditions.
-
**Saved position:** 52 preparation outcomes closed; story56 and survival57 drafts submitted, review58 unfinished; readiness38 reopened and two earlier drafts parked. The earlier request to reopen Claude can wait until resumption.
+
The owner has now 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. The answers are recorded in the [Owner Brief](/Hold%20The%20Flood/Brief).
-
## Previous active-work checkpoint
+
## Current work
-
**10 September 2026, 13:59. The reviewed build and expedition correction batch is integrated. Story and survival rewrites are now underway. All times are Jerusalem.**
+
**Current correction: 0 of 3 outcomes complete.** These are design and review outcomes, not a percentage of the finished game.
-
We are addressing three owner concerns: a convincing survivorslike with hordes and spectacular builds, a readable wiki, and a clear account of the player's fun, excitement, challenge and emotions.
+
| Outcome | Who | State | Next delivery, Jerusalem time |
+
|---|---|---|---|
+
| 59 — Three builds with different pleasures | Systems Designer | Working; receipt and active task verified | Draft today 12:35; range 12:15–12:50 |
+
| 60 — Three worthwhile successive expeditions | PM | Writing against the two new owner answers | Draft today 12:40; range 12:20–13:00 |
+
| 61 — Independent critique of both proposals | Temporary GPT reviewer | Criteria saved; waiting for the stopped drafts | Critique today 13:10; range 12:50–13:40 |
-
## Completed today
+
The original Claude Design Lead and Reviewer are absent from the current native session directory. No assignment has been sent to another Claude session. The work above can proceed with PM, Systems and the temporary reviewer. No additional permanent agent is needed for this batch.
-
- **Discovery and home:** two rewritten articles, a combined critique and author response, accepted at 10:48. Read [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).
-
- **Combat and encounters:** a rewritten [Fighting the Horde](/Hold%20The%20Flood/Combat%20Rules), crowd roles and ten encounter placements. The single review and author response are complete. PM corrected the remaining source, rescue and mechanism inconsistencies and accepted this written outcome at 11:57.
-
- **Builds:** [Build Rules](/Hold%20The%20Flood/Build%20Rules) and two supporting references accepted at 12:05. The stored-energy climax now uses one manual command and automatically resumes charging; repeated menu rewiring is removed from that example.
-
- **Rooms and player information:** the corrected room inventory, player-information article, equipment catalogue and save-state reference were accepted at 12:51, following one review and author response. Shared encounter and reward rules are aligned.
-
- **Three builds and successive expeditions:** accepted as written proposals at 13:53. Read [the horde-scale build examples](/Hold%20The%20Flood/Hordes%20and%20Builds) and [three successive outings](/Hold%20The%20Flood/Expedition%20Proposal). Their equipment, power, heat and projectile rules are reconciled. Passenger transport is an optional proposal; cargo delivery is separate. Later-outing growth remains unresolved.
-
- **Reading links:** a [four-page starting route](/Hold%20The%20Flood) and scoped repairs to eight reference pages. This is not a claim that every reference is now readable or coherent.
+
The outside [Open Decisions](/Hold%20The%20Flood/Open%20Decisions) review has been read and its fourteen groups triaged. Most room, character, language, interface and consistency work belongs to the team. The reported 49-page cleanup has not yet been independently verified by PM; current pages will be checked as their topics are revised.
-
Temporary combat upgrades reset on **every return home**, alive or revived. Physical carried equipment, components and loot are retained. This owner decision is recorded and no longer needs an answer.
+
## Delivery forecast
-
## Open and closed work
+
Updated 15 September, forecast F2. Estimates assume work continues today and about five further active working days for the first full pass. The dates will change when actual delivery or remaining decisions change the work.
-
| Task | Responsible | Current state | Next delivery |
+
| Milestone | Target | Plausible range | What will be ready |
|---|---|---|---|
-
| 47 — Builds and expedition growth | Systems / PM | Closed at 12:05; final connected-build rules and examples published | Written proposal accepted; growth preference still open |
-
| 48 — Hordes and encounter pressure | Design Lead / PM | Closed at 11:57; actual room layout work follows below | Written proposal accepted |
-
| 49 — Combat/build review | Reviewer | Closed at 11:27; one author-response cycle completed | No repeat review |
-
| 50 — Rooms and return routes | Design Lead / PM | Closed at 12:51 after author response and verification | Complete as a written proposal |
-
| 51 — Room and information review | Reviewer | Submitted 12:31; closed after PM checked its findings | Complete; no repeat review |
-
| 52 — Player information and supporting rules | Systems / PM | Closed at 12:51 after author response and verification | Complete as a written proposal |
-
| 53 — Three builds at horde scale | Systems / PM | Closed at 13:53 after response and integration | Written proposal ready for reaction |
-
| 54 — Three worthwhile expeditions | Design Lead / PM | Closed at 13:53 after response and integration | Transport unselected; growth weakness remains |
| 38 — Full design readiness | PM | Reopened after owner feedback | First-pass wiki 15 September |
-
| 39–40 — Earlier detailed samples | Systems / Design Lead | Parked and unaccepted | Reassess after correction |
-
-
**58 tracked outcomes: 52 preparation outcomes closed, 3 current writing/review tasks, 1 reopened readiness review and 2 parked drafts.** These are writing/review counts, not a percentage of a finished game.
+
| New build and expedition drafts | Today 12:40 | Today 12:20–13:00 | Concrete player experiences ready for critique |
+
| Reviewed proposal packet | Today 14:15 | Today 13:15–15:00 | Two proposals, one independent critique, author responses and PM disposition |
+
| Coherent revised design wiki | 23 September | 21–28 September | Readable core articles and supporting rules aligned with selected directions; consequential open choices explicit |
+
| Full detailed campaign design | 24 November | 3 November–22 December | Proposed progression, content, mysteries, ending paths and production scope developed across the campaign |
-
The room draft gives crowds physical arrival paths while preserving walking exits, quiet discovery spaces and short rescue routes. It proposes 16 enemy source volumes behind apertures; these add authoring work but are not extra traversable rooms. Two return routes now show what happens when temporary power resets while cleared ground stays clear. Repeated returns can push fresh combat farther away; that design problem remains open.
+
The near-term forecast has moderate confidence. The full-wiki estimate has low confidence; the detailed-campaign date has very low confidence and is a planning allowance pending a fresh content estimate. Neither means the game is built, tested, balanced or proven to last the desired number of hours. Development and playtests await separate authorization.
-
The electrical weapon’s basic chain attack is restored, missing player cues are back and the revised routes now define their doorways. The five save examples, ten options and twelve physical equipment parts were preserved. These checks close that writing task; they do not establish readable combat in play.
+
The pre-pause estimates were 15 September for the readable wiki and 17 November for detailed campaign design. Five paused calendar days and the outside review's unresolved core-loop findings require new dates. Earlier estimates and actual deliveries remain in this page's revision history.
-
The lightning, ricochet and gravity examples now connect different player actions to their intended pleasure: crossing toward a dense electrical chain, shaping reflected paths, or gathering pursuers before a thermal burst. Their proposed climaxes reach dozens of ordinary bodies; geometry, heat and recovery limit the actual result. These are written possibilities, not measured kills or validated fun.
+
## What must improve
-
The expedition comparison now uses a functioning starter rig and correct equipment timeline. A proposed carriage line shortens repeat walking, while cargo-only delivery remains a separate choice. Neither solves the later outing that starts weak on already-cleared ground. The overall readiness check remains open.
+
- Each expedition provides fresh combat and a rise in power before its major challenge, while permanent discoveries and changes keep their value.
+
- Builds differ in movement, attention, cost and payoff, and permit useful combinations the player can discover.
+
- Hordes create urgency and spectacular releases; earned quiet gives discoveries room to land.
+
- Articles explain what the player wants, notices and does, and why the experience could be exciting. Consistent numbers and completed documents alone do not satisfy this standard.
-
The next two rewrites make the story's curiosity, dread and revelations readable, and explain oxygen/packing through choices, excitement and relief. All three original roles received their assignments automatically. No new permanent agent or routine owner message-forwarding is needed.
+
## Held work and earlier outcomes
-
## Current choice for the owner
+
The full tracker contains **61 outcomes: 52 earlier preparation outcomes closed, 3 current, 3 held, 1 readiness assessment reopened and 2 parked**. Earlier closure records document preparation and integration, not proof the game meets the brief.
-
Should temporary power grow **regularly during fighting**, with bigger upgrades at major horde milestones, or **only after clearing or sealing a horde**? PM recommends regular growth: for example, two upgrades during a ward fight, then a transformation after its main surge. This provides a more continuous rise in power, at the cost of more frequent choices. The current stage-only draft remains provisional. Both options reset temporary upgrades whenever you return home.
+
| Outcome | State | Reason |
+
|---|---|---|
+
| 56 — Hospital story article | Held; previous draft submitted | Reconcile the current outside edits before review or acceptance |
+
| 57 — Survival and loadout article | Held; previous draft submitted | Reconcile current text and new expedition rules |
+
| 58 — Earlier story/survival review | Incomplete and held | Prior source revisions are now stale |
+
| 38 — Full design readiness | Reopened | The player's experience and cross-page consistency still need work |
An answer is pending. Room geometry, controls, accessibility, equipment and readability work continue. Only the dependent final growth rules wait for this preference.
+
Previous completed work includes the discovery/home, combat, room/information, and build/expedition drafting batches. The latest owner answers supersede their permanent encounter-clearing and stage-only growth assumptions. Their useful content remains input to the correction.
-
## Estimated deliveries
+
## Next owner decisions
-
| Milestone | Target | Plausible range |
-
|---|---|---|
-
| Combat/build initial drafts | Actual today 11:17 | Lead submitted 11:07 |
-
| Single combat/build author responses | Actual today 11:49 | Lead 11:41; Systems 11:49 |
-
| Room and information drafts | Actual today 12:23 | Systems 12:18; Lead 12:23 |
-
| Combined room/information review | Actual today 12:31 | Earlier than the 14:15 estimate |
-
| Single room/information author corrections | Actual today 12:43 | Lead 12:42; Systems 12:43 |
-
| Integrated room/information correction batch | Actual today 12:51 | Earlier than the 14:00 target |
-
| Three-expedition proposal | Actual today 13:06 | Earlier than the 13:45 target |
-
| Three-build mechanical proposal | Actual today 13:12 | Earlier than the 14:00 target |
-
| Combined build/expedition review | Actual today 13:26 | Closed after PM checked the findings and erratum |
-
| Single build/expedition corrections | Actual today 13:45 | Lead 13:37; Systems 13:45 |
-
| Reviewed build/expedition packet | Actual today 13:53 | Earlier than 14:45 target |
-
| Story and survival drafts | Today 14:35 | 14:15–15:00; Lead expects 14:35–14:55 |
-
| Combined story/survival review | Today 15:10 | 14:50–15:45, dependent on actual drafts |
| Whole readable first-pass wiki | 15 September | 13–17 September |
-
| Detailed campaign design | 17 November | 27 October–15 December |
-
-
The completed batch retains 24 module identities and 40 rooms. The next articles explain existing story alternatives and survival rules through the player experience. They do not decide the pending growth or travel choices. Crowd capacity, traversal timing, readable combat and fun remain untested.
-
-
**Forecast F1.25, updated at 13:59:** the build/expedition packet is integrated at 13:53, ahead of its 14:45 estimate. The next story/survival packet targets 16:00, with a 15:30–17:00 range covering one critique, author response and integration. The full readable wiki and detailed campaign dates are unchanged. Earlier estimates remain in revision history and the forecast record.
-
-
Confidence is moderate for the next batch, low for the first-pass wiki and very low for detailed campaign work pending fresh scope estimation. Dates assume the existing three 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. Implementation, simulation, playtesting and assets require separate authorization.
+
The two immediate combat choices are answered. Next, PM will bring concrete story and rescue alternatives, then the effect of completing the station connection and a costed scope proposal. The fourteen review categories are not fourteen questions the owner must answer before work continues.
