Hold The Horde — Progress

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.

Ready to read

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, continue through three expeditions into the observation ward, then Coming Home and Discovery in a Changing Station. For combat, follow Hordes and Builds into Three Ways to Break a Horde.

Completed package Actual time today What changed
59–61 — Builds and three expeditions 12:08 Different movement and payoff proposals; successive trips pursue different discoveries
56–58 — Hospital story and survival 12:32 Two possible core mysteries; comparable loadouts with a visible cost for the heavier kit
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
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
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
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

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.

Working now

Outcome Owner and current state Next delivery, Jerusalem time
69 — Rescue under pressure Draft delivered 14:03; independent critique in progress Reviewed proposal 15:15, range 14:45–16:15
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

Read the scene in Hordes and Builds, with placement in Moving Scan Expedition. 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.

Delivery forecast

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
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
Moving-scan proposal Delivered 13:39 Earlier than 14:15 target Concrete location, rising fight, build climax, discovery and next trip
Reviewed moving-scan proposal Completed 14:01 Earlier than 15:30 target One critique, one response and verified integration across six articles
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
Short-rescue proposal Delivered 14:03 Earlier than 14:30 target One personal rescue scene and two comparable failure approaches
Reviewed short-rescue proposal Today 15:15 14:45–16:15 One critique and response; an understandable owner choice with costs
Coherent revised design wiki 23 September 21–28 September Readable core and supporting rules aligned; consequential 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

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.

What still needs work

  • Broader expeditions must sustain fresh combat, meaningful growth and different discoveries around persistent changes.
  • Build combinations need distinct decisions and room for surprising interactions. The new alternatives still need selection and detailed integration.
  • Rooms, people, languages and story consequences need concrete scenes with emotional and discovery payoffs.
  • 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.
  • Full readiness requires a coherent player journey and honest scope, beyond internally consistent tables.

Owner choices

The two immediate combat questions are answered in the Owner 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 is the wider issue index; its recommendations remain proposals. Its fourteen categories are not fourteen answers needed before work can continue.

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9