| Mechanism families / major placed mechanisms | 5 / 13 | 9/24; 14/40 | Thirteen major instances need geometry, warnings, stages, persistence and rearming; fixed room services and ordinary joins remain separately owned interfaces |

The current SMALL first pass is **4 regions / 24 modules / 40 rooms / 12 objectives / 4 ship assemblies / 5 people / 15 scenes / 12 equipment definitions / 6 ordinary + 3 special roles / 10 encounters including 2 setpieces / 5 mechanism families / 13 major placed mechanisms / 4 language + 4 story chains / 5 home projects / 2 special connection challenges**. These are prepared proposal counts, not an owner-selected game size. Thirteen is not every interactive object: R26/R33 service transformations, the R02/R03 board/rack, ordinary doors and join faces stay owned by their room/interface descriptions rather than becoming extra P-identities. Campaign36 response536 reports **26 deduplicated evidence entries**, but PM disposition and its narrow source-verification clarification539 remain pending; 26 is therefore a submitted count, not an accepted final ledger.

The 15 SMALL survivor scenes include rescue and home follow-through. Home-project scenes should be assigned within that ledger where possible; if an additional scene is necessary, record the increment instead of silently exceeding fifteen. Branches are variations of a named scene, but each materially different consequence still needs writing and state review.

| Each of13 major placed mechanisms | First-version geometry, warning, action/stages, reset/rearm and persistence boundary, usable alternative/recovery and linked discovery | Full variant/combined-encounter details, exact thresholds and exhaustive state/recovery paths |

A room brief may reference its module and a mechanism brief, but cannot omit its own distinguishing content. V1 retains Design Coverage's thirteen-major-mechanism obligation; the new allowance below makes it explicit. Detailed campaign work extends these accepted briefs rather than charging them again.

**Detailed campaign specification:** every approved placed room, mechanism, clue, scene, reward and ending branch has concrete entry/exit, observation, action, interruption, persistence and recovery behaviour. Shared definitions are referenced; instance-specific differences are authored. Precise tuning may still require later evidence. This is larger than a map of twelve objectives.

|---|---|---:|

| Scope/handoff37 | This two-article refresh, one focused critique, at most one reasoned response and PM disposition. | **14–24 role-hours** |

This is a workload allowance, not a countdown or observed throughput claim. Campaign36 and scope37 are already in flight, so elapsed calendar time may be shorter than dividing these hours serially. The critical risks are a source contradiction that needs a bounded parent repair, a consequential unresolved interface, or unavailable review/integration capacity—not prose volume.

The PM's adopted **F1.14** calendar remains the current management forecast: M2 coherent core **11 September (10–14 September)**; complete first-pass M3 wiki **14 September (11–18 September), low confidence**; M4 detailed campaign **10 November (20 October–1 December), low confidence**. This scope analysis does not silently replace those dates. The 28–50-hour remainder is compatible with the M3 range only if the existing Lead, Reviewer, Systems and PM work can continue in parallel and the coherence pass finds bounded corrections. A new technical/production specialist on 10 September is conditional on a concrete independent gap and is not counted as available capacity. No extra permanent role or two guaranteed specialists are assumed.

M4 extends accepted first-pass briefs into exhaustive authored content; it does not re-charge their existing definitions. A current SMALL candidate needs the following distinct work, with shared observations, scenes and fixtures referenced once:

| M4 workstream | Unique deeper work, excluding current first pass | Judgment allowance |

The range is broad because actual branch density, permitted arrangements, final dialogue depth and Campaign36's accepted evidence ledger are not yet known. It is not derived from agent typing speed, and it does not prove that the 10 November forecast is achievable. That forecast remains a low-confidence calendar judgment: it requires parallel authoring, bounded revision, no fundamental core-rule reversal and timely owner decisions only where work truly depends on them. Three representative detailed packages—a repeatable mechanism room, a two-language investigation with correction, and a short rescue/home arc—should be authored and independently checked before narrowing this allowance or extrapolating campaign duration.

The owner's **30/90/100–200-hour** ambitions remain unproven. SMALL is a costed candidate for estimating authored work, not an owner-selected downgrade or a demonstrated playtime band. TARGET and STRETCH remain alternatives whose branch interactions require their own estimate rather than multiplication from SMALL.