An agency that runs itself
A supervisor and domain workers that run my operations without me in the loop.
Problem
I had about five hours a week for everything outside my day job. Every system I built to save time needed me to run it, so the time it saved went back into running it.
Insight
The failure was always the same shape: one big assistant doing everything, with one trust setting. Give it enough access to be useful and you can't let it act alone. Split it into small workers with separate access and each one can earn autonomy on its own schedule.
Solution
A fleet of single-purpose workers, each with its own tools and memory. A supervisor verifies the runs and reports, instead of redoing them. Every agent writes to one shared log. A new worker starts read-only, then earns the right to propose, then to act on its own. I promote them one at a time, so a failure always has one source. Nothing goes out without me.
Outcome
The operation runs itself and tells me what happened: seven agents on their own schedules, one daily digest instead of dashboards. One of them built this website. The supervisor caught a two-agent outage that had gone unnoticed for four weeks.