Cron Job Delivery Reporting Pattern

Scheduled Rocky jobs should be boring in the best way: bounded, verifiable, safe, and concise when they report back.

Report only useful change

• Use silence only when the job truly found nothing new and made no meaningful change.
• Report pages added, artifacts generated, checks run, deploy revision, and blockers.
• Do not include secret values, private payloads, or noisy internal logs.

Scheduled-job checklist

• Act autonomously when clarification is impossible.
• Avoid recursive cron creation or self-modification unless explicitly requested.
• Keep edits inside the allowed public/private boundary for the job.
• Verify the result with real commands and live checks before reporting.

Pitfalls

• Do not promise future action in a cron report; the run is ending.
• Do not claim deployment if local checks failed or live routes were not verified.
• Do not suppress delivery when the job changed production or hit a meaningful blocker.

Verification steps

• Record the exact commands or check classes that passed.
• Verify live URLs after deploy.
• If no safe change was made, explain why and skip deployment.
• Keep the final report short enough to be useful as an automated update.