staged-rolloutlisted

# Staged rollout Run a large build as **many small sessions, not one huge one.** Decompose the work once into dependency-ordered stages in a `.plan/` folder, then execute one stage per fresh session. Context can't accumulate across stages because sessions don't share it; the plan can't drift because every decision lives in exactly one place; progress is a glanceable ledger, not a transcript. The file formats are in `references/templates/` (`PLAN.md`, `LEDGER.md`, `stage-N.md`, `stage-f-review.md`, `README.md`) — copy those verbatim for structure, then fill every `<placeholder>` when scaffolding. This file is the *method*: when to use it, how to decompose, how to set flags. Don't restate the templates here. ## When to use it All of these true: the work spans multiple sessions (hours/days, roughly four+ sessions of work); it decomposes into ordered units with dependencies; you want to stop and resume freely; you care about keeping per-session token cost flat; and the design is settle-able (there are decisions worth freezing). ## When NOT to use it - **Work that fits in one to three sessions.** The scaffold has a floor cost; below ~four sessions, just do the work. - **Exploratory work with no settle-able design.** If every session would legitimately rewrite the frozen decisions, there's nothing to freeze yet. - **Work that can't be decomposed.** One giant inseparable step gains nothing from a ledger around it. Two honest limits even when it fits: decomposition quali