stakeholder-updatelisted

# Stakeholder Update The same truth, calibrated per audience. Emphasis and detail change with the reader; the numbers and the bad news never do. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Numbers reconcile:** every figure in the update appears in, or derives arithmetically from, the input state. No invented progress: nothing "on track" that the state marks late, no sentiment claims ("customers love it") without a signal in the state. - **G2 — Calibration without drift:** audience versions differ in emphasis, ordering, and detail level — never in facts. Bad news present in the state appears in every version; a risk visible to engineering but hidden from the exec update fails the gate. - **G3 — Context travels with comparisons:** a number measured against a target or assumption keeps its time frame and basis (11% at day 12 of a 90-day 15% assumption — not "missing target", not "strong adoption"). Delays carry cause + recovery, not omission. ## Steps 1. **Reconcile first.** Extract every number, date, target, and issue from the state into a fact table. This table is the update's source of truth — both versions cite it, and the gate check re-derives against it. 2. **Sort facts by audience relevance,** not by comfort: exec (risk, trajectory, decisions needed), sales (customer-visible wins, timing, talking points), team (details, blockers, credit). Relevance ranks facts; it never removes the uncomfortable ones. 3. **Frame comparisons hones