The Rocky Daily Operating Brief

A daily brief is one of the safest first Rocky automations. It informs humans without taking risky action on their behalf.

What the brief should include

A useful brief is short and decision-oriented:

• What changed: new leads, messages, orders, reviews, site changes, tickets, or files
• What is urgent: deadlines, failures, broken links, angry customers, payment issues, blocked automations
• What needs approval: draft replies, posts, purchases, config changes, customer actions
• What can wait: low-priority notes, FYI items, long-term improvements
• Recommended next action: one or two concrete suggestions

Delivery options

Send the brief where the owner already looks: Discord, Telegram, Slack, email, or a private dashboard. For Hermes gateway setups, home channels and platform-specific delivery rules should be configured deliberately.

Cron shape

Schedule: every weekday 8am
Scope: read-only discovery and draft recommendations
Output: summary to approved channel
Risk: no sending, buying, deleting, or publishing

Good first version

Start with one source: website health, inbox summary, review monitoring, or lead follow-up. Add more sources only after the brief is useful and trusted.

Verification

Review the first week manually. Remove noisy sections, add missing context, and document approval rules before expanding automation.