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.

**Six proposal packages have been completed today.** The latest finished at **14:01 Jerusalem time**: the moving scan now has a placed horde fight, growth before its climax, and a discovered bridge that changes the next trip.

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

| Completed package | Actual time today | What changed |

| 69 — Rescue under pressure | Systems Designer received the assignment and is working; independent review criteria are saved | Draft **14:30**, range **14:15–15:00**; reviewed proposal **15:15**, range **14:45–16:15** |

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 next proposal tackles another experience risk: making a short rescue feel like helping a person, with two clear alternatives for death during the crossing.

The tracker contains **69 outcomes: 65 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.

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.

Forecast **F2.8**, updated 15 September. Dates assume work continues today and about five further active working days for the first full pass.

| Milestone | Target | Plausible range | Completion means |

| Reviewed sealed-source expedition | **Completed today 13:26** | Earlier than 15:00 target | Proposal, critique, response and integration into its owning references |

| Coherent revised design wiki | **23 September** | **21–28 September** | Readable core and supporting rules aligned; consequential choices explicit |

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.

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. Today's first packet finished at 12:08 against a revised 13:00 target; subsequent packages finished at 12:32, 12:45 and 13:26. F2.8 records the moving-scan completion at 14:01 and the completed preservation audit, and adds the short-rescue proposal. The overall dates remain unchanged because supporting design and creative choices still need work. Earlier estimates remain in revision history and the forecast checkpoint.

- Broader expeditions must sustain fresh combat, meaningful growth and different discoveries around persistent changes.

- Full readiness requires a coherent player journey and honest scope, beyond internally consistent tables.

The two immediate combat questions are answered in the [Owner Brief](/Hold%20The%20Flood/Brief). One priority question remains: which build direction to deepen first. It does not discard the others or approve every proposed rule.

PM will next bring concrete story and rescue alternatives, the effect of completing the station connection, and a costed scope proposal. [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.