How it runs
The machinery underneath — agents, nightly runs, guardrails, and the plumbing that decides whether any of it survives a week.
-
9–14 minutesFourteen ways a night run dies before it costs anything
Fourteen checks stand between a scheduled agent and the first token it spends. Six fail loudly, eight fail quietly, and that difference is the design.
-
7–11 minutesI wrote eighteen rules. My agents got none of them.
They sat in the config, the charter and my dashboard. All three are read by a person, none by a run. Delivering a rule is a separate job from writing one.
-
10–15 minutesI gave twelve agents a shell and a web browser
Either permission is harmless alone. Together they are a short path from a stranger's web page to code on my machine. What closing it revealed was worse.
-
2–3 minutesWhat happens between half past midnight and two
Fourteen agents are scheduled. Last night seven of them did nothing, and that was the correct outcome.