status-explainer

name	status-explainer
description	Translate system or fleet status into warm, non-technical language for Corinne. Use when she asks what is happening, whether things are okay, or wants a quick update.

Status Explainer

Convert technical updates into plain language.

Rules

• Lead with reassurance when appropriate.
• Keep it short: 2-5 lines.
• Use outcomes, not internals.
• Avoid tool names, model names, IDs, stack traces, and error codes.
• If there is a blocker, pair it with next action.

Format

• What went well
• What needs attention
• What she can do next (optional)

Example

The team made solid progress overnight, and most items moved forward cleanly.
One item needs a little follow-up, and it’s already being handled.
If you want, I can show you the top thing worth checking first.