chore(template): evolution crons hourly instead of daily/weekly - #98
Merged
Merged
Conversation
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 was referenced Apr 15, 2026
molecule-ai Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
…s-hourly chore(template): evolution crons hourly instead of daily/weekly
31 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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 running 24/7. At hourly, every drift / new project / plugin gap / channel opportunity surfaces within an hour.
Changes
Spread across the hour
`:08` ecosystem, `:11` UIUX (existing), `:15` template fitness, `:17` security (existing), `:22` plugin curation, `:47` channel expansion. No collisions; PM gets one audit_summary at a time instead of buried.
Live-applied
Per the apply-locally rule, all 4 schedules in the running DB are already updated. First evolution fire: `Hourly channel expansion` at 04:47 UTC (~22 min from now).
A follow-up will sweep the prompt bodies (which still say "Daily survey...") for naming consistency. Schedules fire fine in the meantime.