|---|---|---|---|

| 39–40 — Earlier detailed samples | Systems / Design Lead | Parked and unaccepted | Reassess after correction |

**52 tracked outcomes: 46 preparation outcomes closed, 3 current outcomes, 1 reopened readiness review and 2 parked drafts.** These are writing/review counts, not a percentage of a finished game.

The combat proposal now describes massed ordinary encounters and larger climaxes. The room work must give those crowds actual arrival paths and fighting space without consuming walking exits or turning rescues into escorts. It also checks what a player meets after returning home with temporary power reset: cleared travel remains cleared, so the next occupied frontier must be identified honestly.

The information work focuses on what the player needs to see while moving, firing and using specials. Detailed diagnostics should support experimentation without becoming required reading during ordinary combat. Its equipment and save-state repairs keep the visible rules consistent with what the game retains.

|---|---|---|

| Whole readable first-pass wiki | 15 September | 13–17 September |

The initial combat/build drafts and responses arrived ahead of their estimates. Their remaining integration is complete. The next batch inspects eleven room types: ten need crowd-source variants, while the core clamp room needs preservation checks. These are authored design obligations; capacity and traversal timing remain untested.

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.