1 min read
Monthly Cadence
Monthly work audits the operating system itself: graph health, routing behavior, stale automations, generated surfaces, and consolidation opportunities.
Monthly cadence is not for re-running every daily job. It is for checking whether the system still routes correctly and whether the wiki shape still matches the current brain. Source: Wiki Brain Operating Model; Scheduling Operating Model
Monthly Review Areas
| Area | Commands or surfaces |
|---|---|
| Wiki graph shape | npx tsx scripts/wiki-status.ts, npx tsx scripts/wiki-breakdown.ts |
| Broad article quality | npm run wiki-quality |
| Routing behavior | npm run routing-doctor, npm run trigger-eval |
| Generated surfaces | npm run build-index, qmd update/embed, graph/runtime checks, and skill registry checks |
| Scheduler health | npx tsx scripts/check-freshness.ts, Scheduling Operating Model, local scheduler audit |
| Consolidation | Page Consolidation Audit, Wiki Brain Operating Model |
Output Standard
Monthly work should end with a concise log entry naming errors fixed, warnings accepted, stale automations retired/deferred, and generated surfaces refreshed.
Timeline
- 2026-07-01 | Rebuilt the monthly cadence as a system-health audit covering graph quality, routing, generated surfaces, scheduler drift, and consolidation. private page
- 2026-05-31 | Monthly cadence from HEARTBEAT.md. Source: public wiki expansion, 2026-05-31