ORIGINAL: Karri
Furthemore, the Supreme Command needs to 'know' how to give objectives(instead of designer implementing those objective tracks),
How do you do this, though? How does the computer know what is important and what isn't? This is an incredibly human decision, which is why it is made by the designer
at the moment.
The key is information and how to use that information, and it should flow both ways. For example the 1st corps gives the 1st division the task of capturing the city of Kharkov. 1st division 'analyses' the situation and sends back a message that this is impossible without 2nd and 3rd division securing flanks. 1st corps then analyses the situation and decides if it can allow 2nd and 3rd division to do that.
This is how real armies work- but I think it's an inefficient and roundabout way for the computer to work. After all, I Corps, 1st division and everyone else are in fact all controlled by one staff. Further, the situation is much more complicated that deciding whether or not to attack one point and whether or not to assign support to that attack.
So to take your basic concept, I Corps decides on a list of possible actions and sets them priority ratings. It then apportions troops to these tasks according to those ratings. Then it records the highest priority rating which could not be achieved due to lack of troops, and the lowest priority rating which was achieved. GHQ then reassigns troops from areas which were able to do all their priorities to areas which have lots to do.
All of this would be very difficult to make the computer do. The virtue of my proposition is that it fits the existing model where most of the problems have already been solved. It could also apply at least partially to existing scenarios as well as new ones.

