Content Studio — Cron & Scheduling Specification

Content Studio uses three scheduled jobs for end-to-end content lifecycle management. Jobs can be installed via system cron or Clawdbot cron (preferred for AI-native features). | Field | Value | |-------|-------| | Schedule | `0 20 * * 0` — Every Sunday at 8 PM EST | | Script | `scripts/generate-weekly.sh` | | Duration | ~30s (harvest) + async (AI generation) | | Lock | `logs/.generate.lock` (prevents concurrent runs) | **What it does:** 1. Harvests 7 days of memory files, Chronicle moments, and git activity 2. Creates platform output directories (`output/[platform]/`) 3. Writes weekly manifest with themes and platform assignments 4. Dispatches AI content generation via Clawdbot (or writes manual flag) 5. Rotates logs older than 30 days | Field | Value | |-------|-------| | Schedule | `0 9 * * 1` — Every Monday at 9 AM EST | | Script | `scripts/collect-analytics.sh` | | Duration | ~5s | **What it does:** 1. Scans output directories for content from the past week 2. Supports both new (`output/[platform]/`) and legacy (`output/YYYY-MM-DD/`) layouts 3. Generates weekly review JSON in `analytics/weekly-reviews/` 4. Updates calendar state 5. Dispatches AI analytics review if content exists