The software assurance-to-build ratio in regulated arenas is large, and mostly clock. That’s because the trad approach of front-loading discovery breeds Kafkaesque process.

It’s better to make discovery the delivery: treat constraints as executables, generate candidates cheaply, and let evals do the selecting.

What survives is live product and evidence of fitness at once, which sends the ratio negative.

Call it autonomous productisation: directed evolutionary engineering, with assurance as the selection pressure, and the whole hyperstructure running unmanned and asynchronously, managed only by exception.