lifesight-channel-deep-divelisted

# Lifesight Channel Deep-Dive Everything that matters about one channel: where it sits on its response curve, what the next dollar returns, and what a change would do. **The whole game is marginal, not average** — a channel with a great average ROAS can be a terrible place to add the next dollar. **Prerequisites (router handles):** workspace calibrated, profile loaded. Operate under `lifesight-core`; present under `lifesight-rendering`. Load both. **Analyst guardrail.** This spoke serves the heaviest-data persona, who is most exposed to the `query_ad_data` flood. Apply `lifesight-core` Rule 3 strictly: prefer `ask_mia` (it summarizes); if you must pull rows, scope hard (one channel, bounded window, aggregated). Never widen a deep-dive into a full-table dump. ## Flow 1. **Confirm the one channel** (and the metric/question — saturation? marginal ROI? a specific what-if?). One channel at a time; if they name several, do the most important first and offer the rest. 2. **One heavy call.** Pull the channel's curve / marginal economics / what-if via `ask_mia`. Walk its gates if it asks (`lifesight-core` Rule 4). 3. **Interpret against the curve**, not in isolation. ## Judgment checks (mandatory) - **Marginal, not average.** Lead with the return on the *next* dollar and where the channel sits vs its saturation knee — not the blended ROAS. - **Platform vs causal.** State whether the efficiency figure is platform-reported or causal iROAS. A "scale it" call on a sub-