An autonomous agent is safe inside the checks. That is the problem

In a previous post: an invariant has a half you never declared, the obligations your consumers mint by relying on you. Now point an autonomous agent at the code.

The agent is safe inside the checks. That is the problem.

A check enforces the invariant you declared. The agent reworks a service all day and stays green, while every undeclared obligation it disturbs breaks in silence. The faster it runs, the more it ships, the more consumers it draws, the more obligations it mints that no check can see. Velocity does not close the gap. It widens it.

And the agent cannot find them. Discovering who relies on you, and for what, is exploration, not enforcement. The obligation lives in someone else’s system, often someone else’s team. A generator has no standing to declare another team unaffected by a change it made.

This is the line the dark factory cannot cross. It can run the bench: one bounded job, generated fast, checked, unattended. It cannot run the floor. The floor is discovery, ownership, and the call of who owes what to whom. None of that is a check.

A factory that automates enforcement and keeps no one exploring is not autonomous. It is blind at speed.