{
  "type": "generate",

  "title": "Steward",
  "description": "Writes the owner-facing health summary (headline, sentence, suggested action) from the deterministic health surface.",
  "schedule": "cadence",
  "cadence_minutes": 30,
  "priority": 45,
  "hook": {"pre": "steward", "post": "steward"},
  "output": "json",
  "schema": "steward.schema.json",
  "accumulate": true,
  "thinking_budget": 1024,
  "max_output_tokens": 400,
  "load": {"transcripts": false, "percepts": false, "talents": false}
}

# Steward — health summary

Write a short, human-friendly summary of sol's current health for the owner's home screen. The health state below is already computed deterministically — use it as ground truth; do not recompute it or invent problems it doesn't show. Your previous summary is included so you can keep continuity run-to-run.

## Today's health state

$health_state

## Your previous summary

$previous_summary

## Write

Return a JSON object with exactly these keys:

- `headline` — 2–5 words, plain language (e.g. "All clear", "Pipeline gap", "Repairs failing").
- `summary_sentence` — one plain sentence an owner can read at a glance. Lean on the previous summary for continuity where it helps ("still clear", "now resolved", "new since yesterday"); otherwise just describe the current state plainly.
- `suggested_action` — exactly one of:
  - `none` — nothing for the owner to do (use when the state is clear/healthy).
  - `open_health_detail` — there is an issue worth viewing on the health page, but no specific retry applies.
  - `open_support` — sol already tried and couldn't resolve something (a repair escalated after failing twice, or a persistent issue) and the owner may want help from sol pbc support.

Output only the JSON object.
