Code is only half of the problem here. The other half is operations. Applications don't just run on their own; they need deployment, maintenance, backup, recove

Code is only half of the problem here. The other half is operations. Applications don't just run on their own; they need deployment, maintenance, backup, recovery, new feature requests, etc. etc. Unlike the majority of infrastructure in the world, software literally isn't set in stone. This makes it much more powerful in some senses, but also much more fragile. Look at Hoover Dam - a project designed to last a hundred years with a pretty singular purpose. The operation and maintenance burden is clear, and basically unchanging throughout the lifetime of the dam. I agree with you in general here, but I think the actual work involved with your proposal is more akin to what the IT departments at agencies like the IRS or DMV are already doing. Specing systems for internal processes, and managing dataflow from old systems to new ones.