molecule-ai/molecule-core
35
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity

chore(template): switch evolution crons from daily/weekly to hourly

Browse Source 
CEO 2026-04-15: the team's evolution loops should be hourly, not daily/weekly.
A 24h or 7d cadence is the wrong rhythm for a team that's expected to run 24/7
and keep improving. At hourly, every drift, every new project, every plugin
gap, every channel opportunity gets surfaced within an hour of becoming visible.

| Schedule                          | Was            | Now          |
|-----------------------------------|----------------|--------------|
| Hourly ecosystem watch            | 0 8 * * *      | 8 * * * *    |
| Hourly plugin curation            | 0 9 * * 1      | 22 * * * *   |
| Hourly template fitness audit     | 30 8 * * *     | 15 * * * *   |
| Hourly channel expansion survey   | 0 10 * * 1     | 47 * * * *   |

Spread across the hour (:08, :11, :15, :17, :22, :47) so the four evolution
crons + UIUX :11 + Security :17 don't collide and don't all bury PM with
audit_summary deliveries at the same instant.

Renamed from "Daily..." / "Weekly..." to "Hourly..." to match the new cadence
and so the prompts (which still say "Daily survey" etc.) read consistently.
A follow-up will fix the body wording.

Live-synced into running DB via PATCH (3 of 4) and direct UPDATE on the 4th
(Dev Lead workspace requires a token the script didn't have). next_run_at
recomputed for all 4. First fire: 04:47 UTC (channel expansion).
This commit is contained in:
rabbitblood 2026-04-14 21:33:31 -07:00
parent 6a8555ef61
commit 0c5a1fdab0
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
org-templates/molecule-dev/org.yaml
View File

@ -128,8 +128,8 @@ workspaces:
5. Use commit_memory to save key product facts for later recall
6. Wait for tasks from PM.
schedules:
- name: Daily ecosystem watch
cron_expr: "0 8 * * *"
- name: Hourly ecosystem watch
cron_expr: "8 * * * *"
prompt: |
Daily survey for new agent-infra / AI-agent projects worth tracking.
@ -163,8 +163,8 @@ workspaces:
files_dir: technical-researcher
plugins: [browser-automation]
schedules:
- name: Weekly plugin curation
cron_expr: "0 9 * * 1"
- name: Hourly plugin curation
cron_expr: "22 * * * *"
prompt: |
Weekly survey of `plugins/` and `workspace-template/builtin_tools/` for
evolution opportunities. The team should keep gaining capabilities.
@ -210,8 +210,8 @@ workspaces:
5. Use commit_memory to save the architecture summary and recent changes
6. Wait for tasks from PM.
schedules:
- name: Daily template fitness audit
cron_expr: "30 8 * * *"
- name: Hourly template fitness audit
cron_expr: "15 * * * *"
prompt: |
Daily audit of `org-templates/molecule-dev/`. Catches drift, stale prompts,
missing schedules, and gaps that block the team-runs-24/7 goal. Symptom
@ -327,8 +327,8 @@ workspaces:
5. Use commit_memory to save CI pipeline structure
6. Wait for tasks from Dev Lead.
schedules:
- name: Weekly channel expansion survey
cron_expr: "0 10 * * 1"
- name: Hourly channel expansion survey
cron_expr: "47 * * * *"
prompt: |
Weekly survey of channel integrations (Telegram, Slack, Discord, email,
webhooks). The team should grow its external comms surface where useful,