| Language chains across at least two languages | 4 | 8 / 12 | Evidence, alternatives, discriminating action, correction and useful transfer |

V1's room/mechanism inventory must contain actual briefs, not only count allocation:

The prior **144–247 role-hour** envelope is retained as a **dated 8 September planning history**. It described work beginning before Regional25 through scope/handoff and combined authoring, review, response and PM integration. It was never a timesheet, and accepted outcomes cannot now be charged again in full. Fast assignment-to-post turnaround records elapsed pipeline time; they do not measure the productive labor needed for every branch, source check or later content implementation.

As of Campaign36 closeout on 9 September, v1 has usable first-pass contracts and finite inventories across all fifteen domains. That is not M3 closure. Verified alignment514 reconciled the global continuity candidate across its named save, connection, rescue, cast, room, encounter, opening, information, death and shifting parents. Verified alignment528 reconciled the accepted mechanical quantities/interfaces across its named catalogue, survival, acquisition, combat, home, room, encounter, build, connection, information, save and continuity parents. Campaign36/PM545 then closed the actual-ID/evidence/state crosswalk for eight chains, fifteen scenes and 26 index entries. Those bounded changes discharge their named contradictions; they do **not** automatically satisfy every broader “M3: reconcile” line in Design Coverage.

The earlier **14–24 role-hour** scope37 allowance is retained as a dated 9 September full-cycle estimate for initial authoring, one critique, one response and PM disposition. Initial authoring and critique are now complete; they are not charged again as forward work.

| Scope/handoff37 response and disposition | This one consolidated response, exact source/diff/readback verification and PM acceptance/integration. | **4–8 role-hours** |

This is a forward workload allowance, not a timesheet, a subtraction from chat turnaround or an observed throughput rate. After this response is delivered, the remaining37 share is principally PM verification/disposition within the 4–8 row; the range is not retrospectively reduced by guessing how much productive labor already occurred. Any concrete Coverage residue found by the coherence pass stays inside its 10–18-hour bounded-repair allowance unless the pass demonstrates genuinely new scope.

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 14–26-hour remainder is compatible with the M3 range only if the coherence pass finds bounded corrections and PM capacity remains available. 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 |

| Campaign evidence and choice | Full clue distribution, corrections and consequences for 4 language + 4 story chains, deduplicated against objectives and rooms. | **50–85** |

| **M4 SMALL candidate total** | Documentation and authored campaign only; no implementation, assets, recruitment, player sessions or technical validation. | **350–590 role-hours** |

The range is broad because actual branch density, permitted arrangements and final dialogue depth are not yet known; Campaign36 now fixes the index at 26 rows but does not enumerate every M4 occurrence, branch or failure variant. 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.