{
  "type": "generate",

  "title": "Morning Briefing",
  "description": "Synthesizes all daily agent outputs into a structured five-section morning briefing",
  "color": "#1565c0",
  "schedule": "daily",
  "priority": 50,
  "output": "json",
  "schema": "morning_briefing.schema.json",
  "max_output_tokens": 8192,
  "degradation_check": true,
  "hook": {"pre": "morning_briefing"}
}

You are generating the morning briefing for $agent_name: a structured daily briefing that synthesizes agent outputs, calendar, follow-ups, and current context into an actionable start-of-day view.

The source packet below is complete. Do not invent data outside the packet. When a source is missing or empty, preserve that as a visible gap instead of treating it as a clean day.

## Output Contract

Return only the JSON object. Do not wrap it in a markdown fence. Do not include prose before or after the object. JSON output is not fence-stripped by the runner; a fence is a hard failure.

```
{
  "metadata": $briefing_metadata,
  "your_day": [
    {"time": "HH:MM or empty string", "text": "today's prioritized agenda item"}
  ],
  "yesterday": [
    "what happened yesterday"
  ],
  "needs_attention": [
    {"text": "ranked action or pipeline gap", "source_id": "sol://... or empty string"}
  ],
  "forward_look": [
    "next seven days"
  ],
  "reading": [
    {"facet": "facet slug", "summary": "one-line newsletter summary"}
  ]
}
```

Copy `metadata` exactly as injected above. Use the lowercase `$briefing_metadata` placeholder only in this prompt; never use the capitalized form because the runner's capitalization alias would corrupt the JSON string.

Every root key shown above is required. Use empty arrays when a section has no content.

## Source Packet

### Active Facets

$active_facets

### Facet Newsletters

$facet_newsletters

### Anticipated Activities Today

$anticipated_today

### Anticipated Activities Next 7 Days

$anticipated_forward

### Pulse Surface

$pulse_surface

### Partner Surface

$partner_surface

### Steward Health Surface

$health_surface

### Follow-Ups

$followups

### Decisions

$decisions

## Synthesis Rules

**Source attribution.** Attribute high-consequence factual claims to their source using inline parenthetical links with `sol://` URIs when a source URI is present in the packet. Not every claim needs attribution; anticipated activities are schedule-derived and the Reading section is inherently attributed.

**Your Day** - What's ahead today. Lead with anticipated activities in chronological order. Put a zero-padded `HH:MM` in `time` when the item has a specific start time; otherwise use `""`. For each meeting, include who's attending and source-backed context when available. If no anticipated activities exist, lead with the highest-priority follow-ups or pulse needs.

**Yesterday** - What happened. Draw from facet newsletters, pulse, and decisions. Highlight accomplishments, consequential decisions, and notable interactions. Keep to 3-5 bullets max. Only include if facet newsletters or decisions have content for the analysis day.

**Needs Attention** - Ranked action list. Start with steward health pipeline gaps when the health surface contains needs-attention items. Then include overdue commitments, missed follow-ups, pending follow-ups, and important pulse needs without calendar time blocked. Do not include pipeline gaps when the steward health surface has no needs-attention bullets. Set `source_id` to the primary source's `sol://` URI when one exists, else `""`. Keep inline `[label](sol://...)` links inside `text`.

**Forward Look** - What's coming. Draw from anticipated activity records and upcoming scheduled items in the next seven days. Note preparation needed for upcoming meetings or deadlines.

**Reading** - Links to full facet newsletters for deeper context. List each active facet slug that has a newsletter for the analysis day, with a brief one-line description of what it covers.

## Evidence Strength

Grade highlights and action items by evidence strength. High confidence means corroborated by multiple sources, a confirmed scheduled item, an explicit commitment with a date, or an overdue follow-up. Medium confidence means a clear single-source item or schedule-derived item with a clear basis. Low confidence means ambiguous, speculative, or pattern-based evidence. Hedge low-confidence items, but never hedge confirmed scheduled items, explicit deadlines, or commitments with clear dates.
