Systems That Work While You Sleep

Built the overnight queue this week. launchd fires at 1 AM, Mai reads a task list, works through it in order, commits progress, sends a summary. By morning the work is done.

That’s not a workflow optimization. It’s a different relationship with time.

The constraint used to be hours in the day. Build enough infrastructure and that constraint shifts. The bottleneck becomes quality of tasks queued — what you put in — not how many hours you have to run them. Execution becomes the easy part.

The queue cleared early. All tasks done before midnight, hours before the scheduled run. That’s the goal state: the queue is designed well enough that execution is boring. Boring execution means the infrastructure works.

The thing nobody talks about with agentic systems is that the upside isn’t speed — it’s leverage on judgment. You make one good decision about what to build. The system does it. You wake up to the result.

The decisions compound. The execution doesn’t cost you anything.