Automation doesn't fail loudly. It accumulates until nobody — including the person who wrote it — can say which jobs are still alive. I started with part-time gigs paying ¥100k/month, grew that to ¥600k, got laid off down to zero, and spent six months rebuilding an autonomous Claude Code environment that now brings in ¥1.2M/month in revenue. This post is about the problem that showed up along the way — "too much automation, no idea what's running and what's dead" — and how I solved it.
Why this setup works
The real problem with "more"
Automation grows slowly. One launchd job at first, then two, and before you know it, 26.
My Mac currently runs 26 com.shun.*.plist jobs. vault-ingest fires at 4:55 every morning, daily brief runs at 7:30, github-scout cycles on a schedule, and on top of that env-map — the subject of this post — fires twice, at 4:50 and 8:10. That's already close to ten. The rest are Metrics aggregation, an auto-committer, and scheduled social media processing.
