0
Draft a difficult status update that names risk without spin
Help me write a status update for project_name that is going to stakeholders including audience_description. The honest situation is: honest_status (include what's on track, what's slipping, and why).
Write the update following this structure:
1. One-sentence headline that states the real status, not a euphemism (green/yellow/red equivalent, but in plain words).
2. What's on track (brief, 2-3 bullets max, don't bury the real news under good news).
3. What's at risk and why, stated plainly with the actual cause, not passive-voice hedging.
4. What we're doing about it, with owners and dates.
5. What we need from the reader, if anything (decision, resource, patience).
Tone should be tone_preference (e.g. calm and factual, or direct and urgent). Do not use corporate hedge phrases like "we are actively monitoring" without a concrete action attached. Keep the whole thing under 200 words.