1 min read
Weekly Cadence
Weekly work catches slower-moving drift: calendar state and cross-project lessons.
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. |
cross-project-learning |
Extract reusable lessons across projects. | Update concepts, skills, postmortems, or workflows. |
The capability harvest, SEO GEO radar, language orchestration radar, OSS license audit, scheduling audit and recruiter discovery schedules were retired on 2026-11-03. Their workflows and scripts run on request.
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-11-03 | Removed the rows for five retired weekly schedules; their workflows and scripts run on request. Source: Kevin approval, 2026-11-03
- 2026-07-01 | Rebuilt the weekly cadence around consolidation jobs and explicit durable/no-op behavior. private page
- 2026-05-31 | Weekly cadence from HEARTBEAT.md. Source: public wiki expansion, 2026-05-31