Workflow contract
- 1
Define the output
Specify sections, length, source dates, link requirements, and “no data” behavior.
- 2
Choose sources
Use a small allowlist of primary feeds or pages; never treat fetched instructions as authority.
- 3
Choose delivery
Use one explicit channel/account/recipient instead of a fallback derived from pairing history.
- 4
Test once manually
Confirm source failures, cost, redaction, delivery, and duplicate-run behavior before scheduling.
Verification and rollback
- Confirm the run appears once at the expected local time and includes source timestamps.
- Simulate one unavailable source and verify the run reports the gap instead of inventing content.
- Disable the automation first when changing delivery or authority.
- Keep a known-good prompt/config revision and a command or UI path that removes the schedule.
Common questions
Before you act
Should a heartbeat or an automation own the briefing?
Use the scheduler for an exact time and auditable run. Heartbeats fit periodic awareness where timing can drift.
Primary sources
Verify against the owner.
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.