Sub-Daily Cadence
The four-hour loop keeps Slack, Gmail, X bookmarks, and local sessions close enough to current for the wiki to function as operational memory.
The sub-daily cadence coordinates three jobs: source-compile, email-sync, and slack-sync. It is local-first because these sources often depend on browser sessions, local auth, and local transcripts. Source: Sub-Daily Ingest Workflow; automations/source-compile.md; automations/email-sync.md; automations/slack-sync.md
Jobs
| Job | Owns | State keys |
|---|---|---|
source-compile |
X bookmarks, enriched bookmark research, local AI sessions, repeated agent friction. | automations.source-compile, syncs.x_bookmarks, compile.last_bookmark_* |
email-sync |
Gmail collection and durable email signals. | automations.email-sync, syncs.email |
slack-sync |
Slack activity review and durable work facts. | automations.slack-sync, syncs.slack |
Invariant
Collection and promotion are separate. A successful run can collect raw material without promoting wiki facts. A blocked run can update automation state while leaving sync state stale. This is correct because freshness should reveal missing external collection.
Validation
npx tsx scripts/check-freshness.ts
npx tsx scripts/doctor.ts --only automations
Use ISO timestamps for four-hour state. Date-only timestamps are too coarse.
Timeline
- 2026-07-01 | Created the companion page for the every-four-hours Slack/Gmail/source-compile loop. Source: User request, 2026-07-01; sub-daily-ingest-workflow