Cron Workers for Social Engagement
HeyRocky uses small scheduled workers instead of one giant social bot. Each worker has a narrow job, duplicate-prevention state, and explicit rules about what not to do.
Worker types
- Content publisher: posts HeyRocky-owned content once.
- AI News curator: finds useful AI/dev articles and adds them to the site.
- Comment worker: finds one high-signal post and leaves one intelligent comment.
- Reshare worker: resh shares one brand-safe post on a staggered cadence.
Why separate workers
Separate workers make failures easier to reason about. If X UI automation is blocked, the AI News worker can still update the site. If Facebook API posting works, the content publisher can still log that X is blocked.
Engagement rules
- One action per run unless explicitly approved.
- No politics, medical/legal/financial advice, tragedy, culture-war topics, dunking, or drama.
- No generic “great post” comments.
- No duplicate comments or reshares.
- Screenshot verification when using browser UI.
State files
social_publisher/social_content_state.json
social_publisher/x_comment_log.json
social_publisher/x_reshare_log.jsonGood comment shape
A useful comment should add a practical angle:
This is the right direction: agent work needs visible state, not just a chat transcript. The teams that make plans, logs, tests, and approvals inspectable will ship safer automation faster.
