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.

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).

| 62 — Growth and a renewed combat route | [Combat Rules](/Hold%20The%20Flood/Combat%20Rules): regular improvements, a major breakthrough, meaningful crowds and discovery quiet mapped onto existing rooms |

| 64 — Fresh combat after every source is sealed | Systems Designer, then PM | Draft delivered 12:58; review 65 complete; one author correction working | Response 13:35; range 13:15–14:00. Reviewed package 15:00; range 14:00–16:00 |

This work can continue while the owner reacts to the three build directions. The previous package is integrated into the room, encounter and survival references for its named route configuration. The additional case must explain visible fresh enemies without silently undoing seals, closing the shortcut or refilling a cleared area during the same expedition.

The original Claude Reviewer became reachable and received the readability assignment automatically, then stopped at a monthly spend limit at 13:03. Temporary GPT support is completing that review. The Lead was absent from the same directory check. Existing role/model settings are unchanged, and no manual message forwarding or new permanent agent is needed.

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 are checked as their topics are revised.

Updated 15 September, forecast F2.6. 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.

| Milestone | Target | Plausible range | What will be ready |

| First reviewed build/expedition packet | **Completed today 12:08** | Earlier than revised 13:00 target | Both proposals, critique, responses and PM checks |

| Reviewed growth/route packet | **Completed today 12:45** | Earlier than 14:30 target | Proposal, critique, response and checked integration into supporting pages |

| Coherent revised design wiki | 23 September | 21–28 September | Readable core articles and supporting rules aligned with selected directions; consequential open choices explicit |

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 first packet was initially forecast for 14:15 today, advanced to 13:00 as drafts arrived, and completed at 12:08. 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. F2.3 resumed the story/survival review in parallel after reconciling current sources. F2.4 recorded the story package at 12:32. F2.5 records the combat package at 12:45, ahead of its 14:30 estimate, and adds the next concrete case after all four sources are sealed. F2.6 adds the six-page readability response and records the recovered Claude connection followed by its spend limit; temporary support keeps the current targets. The full-wiki and campaign dates are unchanged. Earlier estimates and actual deliveries remain in this page's revision history.

- Each expedition provides fresh combat and a rise in power before its major challenge, while permanent discoveries and changes keep their value.

The full tracker contains **67 outcomes: 61 preparation outcomes closed, 3 current, 0 held, 1 readiness assessment reopened and 2 parked**. Earlier closure records document preparation and integration, not proof the game meets the brief.

| Outcome | State | Reason |

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.

The two immediate combat choices are answered. The owner is now being asked which of the three build directions to deepen first; this sets a priority without discarding the others. 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.