planning-risklisted

<!-- planning:contract --> ## Owns The failure modes of the plan, each with a way to see it coming and something to do about it. **The plan is this deliverable's subject, not its client** — a risk softened to preserve a plan has been deleted. Phases: `PREMORTEM → CATEGORIZE → SCORE → DETECT → MITIGATE → ABORT`. ## Before starting - **Open in the past tense: the plan failed, state why.** Prospective hindsight surfaces materially more failure modes than "what could go wrong" does, and the difference is not small - **Get the plan, not a summary of it.** Risks live in the dependencies and the sequence, which a summary drops first - **Establish who can own a mitigation** before writing owners into the register <!-- deliver:sizing --> - **Declare the tier before anything else**, read off the work and stated at the top of the deliverable. `S` — under a day, reversible: one brief in the response, **no files, no handoff**. `M` — multi-day, single owner: the brief and the plan. `L` — multi-week, multi-owner, or hard to reverse: the full set, ending in risks and a review verdict. **Over-planning an `S` is a failure of the same weight as under-planning an `L`** - **The planning gate stops the run at the phase that owns the condition** — the goal cannot be stated in one sentence without "and", no success criterion is measurable, a load-bearing assumption is cheap to verify and unverified, or the person has already decided and is asking for execution; `_planning/