Give every state in your workflow a named consumer on a schedule. That is the first rule I hold for an agent-run software factory, and it is the first of four I tightened in September. The short answer is that agents are very good at creating work, and nothing
Alert on the presence of expected output, not on job failure. That one inversion is the cheapest monitoring upgrade I know, and I now build it into every scheduled thing I own — because a job that fails is already screaming at you, and a job that quietly stops being scheduled
Give every agent its own identity, mint it locally, scope it to write and never admin, and test the kill switch before you need it. That is the whole rail, and I install it before a new agent gets anywhere near a repository. The reason it looks like that — rather
Go find your CI kill switch before you need it, and confirm it is reversible. Mine is a single repository setting that disables Actions entirely, and I know it works because I have exercised it: last week my own estate started minting pull requests faster than anyone could read them,
