1 min read
Weekly Cadence
Weekly work catches slower-moving drift: calendar state, capability changes, cross-project lessons, research signals, recruiting, licensing, and scheduler health.
Weekly jobs should consolidate patterns instead of producing fresh noise. If a weekly scan has no durable signal, record No durable wiki update needed and update state. Source: Scheduling Operating Model; automations/_schema.md
Weekly Jobs
| Job | Purpose | Durable behavior |
|---|---|---|
calendar-sync |
Refresh calendar context when credentials exist. | Update raw/calendar and durable schedule facts when useful. |
capability-harvest |
Discover new tools, MCPs, CLIs, and agent capabilities. | Update Active Stack (What to Actually Use), tool pages, and routing when promoted. |
cross-project-learning |
Extract reusable lessons across projects. | Update concepts, skills, postmortems, or workflows. |
seo-geo-radar |
Monitor SEO/GEO/AEO signals. | Update SEO/GEO pages and content strategy only when criteria pass. |
language-orchestration-radar |
Track CoTCodec/language-orchestration research. | Update research pages and bibliography when relevant. |
recruiter-discovery |
Find recruiters at target companies. | Update career/recruiter context when current. |
oss-license-audit |
Review open-source license risk. | Update repo/project risk pages or output no-op. |
scheduling-audit |
Inspect automation and scheduler drift. | Update Scheduling Operating Model, Operational Heartbeat, or automation files. |
Review Question
For each weekly run, ask: did this change what Kevin or future agents should do? If not, keep it output-only.
Timeline
- 2026-07-01 | Rebuilt the weekly cadence around consolidation jobs and explicit durable/no-op behavior. Source: User request, 2026-07-01
- 2026-05-31 | Weekly cadence from HEARTBEAT.md. Source: public wiki expansion, 2026-05-31