lifesight-forecast-scenariolisted

# Lifesight Forecast & Scenario Planning Help the user see forward — a revenue projection, the budget needed to hit a target, or a head-to-head between options — before they commit real money. **A forecast is a projection with a range, never a promise.** The discipline here is honesty about uncertainty and comparing options on the right axis. **Prerequisites (router handles):** workspace calibrated, profile loaded. Operate under `lifesight-core`; present under `lifesight-rendering`. Load both. ## The three shapes this takes 1. **Forecast** — "what will revenue be?" Project forward from a stated allocation. 2. **Target-KPI planning** — "what budget hits $X revenue?" Solve backward from a goal. 3. **Scenario comparison** — "current vs +15% vs my custom plan." Put options side by side. Identify which one the user is asking before pulling anything. ## Flow 1. **Confirm the basis.** A forecast is meaningless without its assumptions: which allocation (current, or an optimized plan?), what budget, what period, which model. Lock these first (from the profile + one clarifying question if needed). 2. **One heavy call** via `ask_mia` (forecast / scenario / target-KPI). Walk its gates (`lifesight-core` Rule 4). One analysis per turn. 3. **Frame the result as a range with assumptions**, not a point promise. ## Judgment checks (mandatory) - **Always a range + assumptions.** State the confidence range and the assumptions it rests on (budget, period, model, which scenario