Don't get me wrong, I don't support it, but at this point, I've heard enough from the upper-stakeholders to get what they're imagining in their head. Basically, think of a system that takes a long list of requirements, then just magically makes a working code out of it. Then automagically takes bug reports, fixes them, and adds it to the list of the requirements. Rinse and repeat to make sure things just work. The higher up you go in the chain of command, the more you realize that, genuinely nobody cares about code quality, engineers and etc. in any of the companies that are not solely tech companies.

Again, the selling point to higher ups is that you won't need to deal with code anymore, because things will just "work". How? I don't know, but that's what they're imagining and trying to cash into.

Not to me, to anyone who is buying up the solution. We work in very general paradigm of "write code, see something wrong, fix it up, deploy, now it works without that problem". The one that's being desired is "here's list of things i want to work, make it automagically work". How it gets there, doesn't matter, because, only us, engineers, care about code. If it needs to be reimplemented to fix up a bug or introduce a new feature, let it be.