And yet, the only way to actually complete that charter is to "interpret" or "compile" that charter into something imperative.
Prolog is the best way to describe these constraints. Nothing else comes close to its declarative power.
The industry will catch on, eventually.
I beg to differ. The real world is declarative. But as software developers we mostly suck at creating declarative ways to express problems. The spreadsheet being the one example of an intuitive declarative UI that non-programmers grok easily.
Your average corporate VP of engineering uses a declarative interface to issues charters to his developers: "You need to hit X performance target, Y cost of goods, and Z MTBF. By Date D. Go."
Declarative is the way the world works.