Decision
Hermes cron job outputs (proposals, follow-up digests, booking notifications) must be sent to the relevant team channel (#megaphone, jolt, lore, etc.) based on the booking source or subject matter. NOT to hermes-cron-log. hermes-cron-log is a system log channel, not an operational delivery channel.
Context
Hermes posted a proposal draft for “AI Standards” and a Megaphone follow-up digest into hermes-cron-log. Michael corrected this in thread, directing future outputs to the appropriate channel. Calendly booking types exist for Jolt and Lore (not Hockey Stick), so source can be inferred.
Additional directives from same thread
- Use CEO-level concision in these messages - no walls of text
- Calendly shows Jolt and Lore booking types; no Hockey Stick Calendly type exists
- Docs shared by Hermes should be commentable by “anyone with the link” by default
- All docs and files created by Hermes should be under michael@ryevalley.co (not hermes@ or other accounts)
Consequences
- Hermes must inspect booking source or job context to determine correct Slack channel before posting
- Existing cron jobs that post to C0BMPHWFS0H by default should be audited and corrected
- Source: https://ryevalley.slack.com/archives/C0BMPHWFS0H/p1791049840832479 (thread replies)