I like this framing a lot because most teams discover repo readiness way too late, usually after the agent is already wandering. The useful shift is treating readiness as something machine-readable before the run starts: what parts of the repo are safe, what needs approval, what counts as success, and what should stop the loop. If that contract is missing, the agent isn't really autonomous. It's just improvising in a place where the blast radius is unclear.