Leaving aside the problem that you are choosing a date system depending on who is using the dating system and for what purpose, under that condition the most logical would be MM/DD/YYYY, which is truly terrible, so I’m going to politely ignore your argument.
I’ve always disliked how this is described as a paradox. It only highlights a broader point found in many systems, a just system is never about “the good” outnumbering “the bad”. It’s about a balanced equilibrium, as are most relationships. Besides, allowing intolerance is not a tolerant act, that’s not the way we define that term. To make such a claim would be as ridiculous as a racist person saying they are practicing tolerance by not challenging or question any of their bigoted thoughts and instead just letting them play out.
I always thought this for the financial market: Standard & Poor
Moody
The Fed (as in, the past tense of feed)
So the first point was that depending on your files/archives and how you access it, year or month or day may be more relevant to the user, which is why I was saying it’s dependent on the user, so I don’t agree that a human centric solution is always going to say the year is less relevant.
And then if we are going to prioritize organizing the numbers in such a way as to save the eyes a millisecond of time, for standard usage month would be the orienting date since you need to make sure you are looking at today’s month, and then day would be the next necessary date, and then you’d still need the year there, so you’d end up with Month Day Year. Putting Day first would be just as wrong as putting year first because it is irrelevant until you establish the month, it’s too granular.