Maybe - if we do approach things from an automatic assignment of values method, this would be ... tougher. This is the kind of thing the human mind finds easier to mass calculate all the elements in play on to consider than a more simple evaluation of tag to value.Is it possible for the tags to be dynamic? The earliest example I'm thinking of is the Cave Dwelling tech, which is great militarily for both Attack and Defense. But once someone else builds the Neanderthal Culture wonder, it has much less military value, and that all on defense now with caves and the option to promote to City Garrison.
If you look at the first Trait document: C2C Traits (tags & devel), it should show how an automatic costing can work basically. This was using the old system and Khalig has a more updated method that might not even be as mapped out as this page does, but the trick is basically to look at every tag and say, what would a given value in this tag mean for a translation of value into what sort of flavor and create an interpretation system tag by tag. So for example, a Great General additional chance of emergence within your borders of 10% may be 1 full point towards MILITARY_QUALITY. What we're going to have to do to approach things this way is start like this, evaluating every single tag and how that tag can vary, then build out that system of 'costing' and deriving a value for each flavor for all building tags, all unit tags (units mostly so that it can then compile onto techs), civic tags (which we have a lot of similar tags on traits so would be the easiest place to start), religion and corporation tags. Probably even promotions since those also are key features to be considered... Other tech tags not considered elsewhere.
That sounds almost as herculean a task as going through all the objects and just assigning flavors based on human impression but it wasn't too bad to establish a setup on traits (though there are key reasons the traits are applied to human logic before we bake in the totals in spreadsheets and then xml. And this would be self updating, which certainly supports Somebody613's assertion that we have a lot coming that those future contributors won't necessarily have the same automatic insights on how to assign these flavors. We could keep the flavor tags on the objects in the xml for non-default modifications to whatever the code comes up with as well.
I suppose for getting boots on the ground we could start off with civic tags, creating a translation to flavors one tag at a time here.