1 min read
Daily Cadence
Daily work turns recent project activity, external signals, career opportunities, content status, and meeting data into either durable wiki changes or explicit no-op outputs.
Use check-freshness for the live list. The daily cadence describes what should exist, not what actually ran today. Source: Operational Heartbeat; scripts/check-freshness.ts
Daily Jobs
| Job | Purpose | Durable behavior |
|---|---|---|
project-briefing |
Summarize last 24h project commits. | Output brief; promote project/status lessons when durable. |
code-bugfix |
Scan recent commits for likely defects. | File fixes or output findings. |
signal-radar |
Scan general tech signals. | Promote only durable tools, papers, patterns, or routing changes. |
frontend-frontier-radar |
Scan frontend/design-engineering signals. | Update design/tool/concept pages when criteria pass. |
skill-maintenance |
Mine recent sessions for repeated agent friction. | Update skills/routing when patterns repeat. |
meeting-sync |
Pull Circleback transcripts when configured. | Raw transcript plus durable person/project/action updates. |
content-pipeline |
Maintain content recommendations and backlog. | Update backlog only when publishable work changes. |
career-pipeline |
Scan roles and career signals. | Update career pages when role/recruiter evidence matters. |
daily-work-summary |
Summarize shipped work. | Output summary; promote durable project facts. |
Closeout
Every daily job follows Automation Proof Contract. No-op is allowed. Silent non-runs are not.
Timeline
- 2026-07-01 | Rebuilt the daily cadence as a job-to-durable-behavior matrix and moved four-hour work to sub-daily cadence. Source: User request, 2026-07-01
- 2026-06-30 | Split Slack, Gmail, and source compile into the every-four-hours ingest loop. Source: User request, 2026-06-30; Operational Heartbeat
- 2026-05-31 | Daily cadence table from HEARTBEAT.md. Source: public wiki expansion, 2026-05-31