A nightly cron agent that maintains an Obsidian vault: builds cross-references, detects duplicates, suggests merges, and writes daily summaries. Phases P1–P6 are complete with 123/123 tests passing; launchd integration is ready. Designed to be non-destructive and conflict-aware — the dreamer never touches files the operator is actively editing.
Capabilities
- Cross-reference graph construction across the entire vault
- Duplicate detection with similarity ranking
- Daily knowledge summaries delivered to operator
- Conflict-aware — skips files modified within the active window
- launchd cron orchestration on macOS
- 123/123 tests covering ingest, dream, and report pipelines
- Schema-validated input via JSON manifest
Current autonomy level
Weakest link
No Ops Bot heartbeat — if the launchd job silently fails, the operator finds out the next morning by missing summary. Google Drive File Stream introduces filesystem latency that has historically caused cron jitter.
Roadmap to L4
- L3 lift — Ops Bot heartbeat at start and finish, classified failure events, structured pino-style logs.
- L3 → L4 — cron health monitoring with SLA (job must finish ≤ 30 min), retry classification, recovery audit log; fallback to read-only mode on partial vault corruption.
- Verification gate — 30 nights without manual intervention; missed-run detection within 12 h.