btickler does not understand the difference between weakly and strongly solving, that is why about weakly solving he erroneously uses the number for strongly solving.
I just understand that all your shortcuts require determinations to reduce the 10^44 positions that are going to be roughly equivalent to just traversing the positions, say plus or minus a handful of orders of magnitude at best.
You don't seem to get this. Your arbitrary reductions will require a massive amount of computation to apply your arbitrary criteria to each position simply to eliminate it from consideration. Worse, at the end, your "good enough" shortcuts will produce a flawed answer that will not be accepted as a solution anyway. Like building a house out of 2x4s and then staple-gunning cardboard for walls, then trying to sell it for a million dollars.
You can produce *something* in 5 years...but not a solution for chess. More like a watered down attempt at a forward moving tablebase to meet the retrograde analysis in the middle. The forward moving attempt will summarily eliminate valid positions in order to get around the fact that you are not working backwards from mate, which by force culls all of the invalid positions for you. Not so for your ill-conceived plan. What you propose would make engines stronger players, but the results would not even come close to being a solution for chess.
You don't have to believe me. The proof is and will continue to be in the lack of anyone who knows how to build such systems paying the slightest attention to your plan.
Incidentally, this is not the province of game theory, so there's no need to follow their dopey definitions. It's much more digital intelligence. It's a computing problem. We're talking about using digital intelligence to analyse chess and that's just another problem in computing and software writing; not game theory.
I wouldn't criticise if it weren't so completely obvious the definitions are screwed up. I can think my way around them but if you start with the premise that the definitions are perfect, you're bound to become confused. It's quite comical watching you and btickler talking past each other and that's partly an effect of the confused definitions. If you want, I'll write a careful criticism of them. I don't know if it would help, though, because there aren't many people who seem to be able to understand that they aren't perfect. When I first saw them I thought they were some computing or philosophy professor's joke.
You've already written a criticism of the terms long ago. It got the attention it deserved then, as well. Take the hint. Everyone gets that you don't like the nomenclature chosen. It's not the greatest. It is sound, however, and I am sure there is some evolutionary reason for the clumsiness of the terms for the average reader.