Build a briefing that earns its notification

Updated October 30, 2026. Educational guidance; use current official documentation and your installed version.

Design one concise private briefing from my authorized sources.
First confirm timezone, delivery destination, frequency, and review expectations.
List the exact accounts and sources. Treat stale or failed reads as unknown.
Reuse an existing schedule rather than adding a competing reminder.
Read bounded metadata, deduplicate unchanged items, and avoid model calls for no change.
Use a short model pass only when synthesis adds value.
Separate confirmed appointments, pending decisions, and suggested priorities.
Do not expose other people's private details or send messages on their behalf.
Keep a text fallback if optional speech fails.
Test manual execution, actual delivery, unchanged input, and a source failure.
Cap daily runs and retries, and define when the schedule stops.
Do not silently switch to paid API access when a subscription limit is reached.

Start with one or two useful sources. More integrations are not automatically a better briefing. See proactive workflows.