North Star Watchdog
Since May 2026
An agent audits my systems every Sunday and files what drifted, including about me.
Running weekly · latest 2026-10-25
- What it does
- Every Sunday an agent reads my architecture doc, compares it against what is actually running on my machine, and files a ranked report of everywhere reality has drifted from the plan. It messages me the top three.
- What I orchestrated
- I wrote the doctrine: a five-class drift taxonomy, an urgency x significance scoring rubric, and a hard rule that the Watchdog may only surface problems, never edit canon or fix things itself. Changes to the architecture require a written amendment proposal that I ratify.
- The stack
- Claude Code scheduled task reading a knowledge-graph MCP server, the filesystem, launchctl, and agent logs. Writes dated markdown, delivers by iMessage.
- The evidence
- 24 weekly state-of-union runs, 2026-05-21 through 2026-10-25. The 8/9 run flagged three failures in my own systems: an agent dark 8 nights, an embedding pipeline blocked on an expired API balance, and a quarterly audit 8 days overdue. All three were real. The 9/13 run made two wrong calls and the 9/20 run said so in writing. It reports on me either way.