Because tidally locked bodies can also have a fast rotation depending on what they are orbiting. So "Tidally Locked (Y/N) with a fast rotation", but the Y/N is superfluous, because it's only actually reporting non-tidally locked bodies with a fast rotation, so every time it would be "Tidally Locked body (N) with a fast rotation", but then the brackets just containing an N are silly and simply don't make sense because there's nothing to relate them to and it never changes, so it could mean No, or Negative, or Nimbus, or anything. So let's use proper grammar and use a prefix added to the beginning of one of the words to convey the same meaning in a much clearer manner, so we use "non-tidally locked body" to convey the object being described clearly without the unnecessary use of brackets and ambiguous single letters, and "with a fast rotation" to describe the behaviour. So it is much clearer to use "non-tidally locked body with a fast rotation." Then we find ourselves needing to shorten it to make it take up less space and still be clear, so it becomes "non-locked body" (because everyone knows we are referring to tidal locking we we refer to locked, so it becomes "non-locked body with a fast rotation." Removing the ambiguous and possibly confusing and unnecessary use of brackets and letters.
I tried to stay away from this, but I blew the Willpower check. That was mostly because you twisted my statement so that you were addressing something I didn't say.
Since a Tidally Locked body makes exactly one rotation per orbital period, a fast rotation is meaningless in relation to "Tidally Locked" because it will always be 1.
If it is not a Tidally Locked body, then any reference to that condition is pointless because it unneeded verbiage.
So, programmatically, you would want to define whether the Rotational Period is less than or greater than 1 because either of those conditions indicate that the body is not tidally locked.
That being the case, my original position stands.
In nice, simple BASIC, that amounts to:
If Rotational_Period <> 1 Then Tidally_Locked = False
How you care to define that output to the reader is a different issue. For myself, it would be to present the Rotational Period with a notice when the value of 1 causes the body to be tidally locked:
Rotational Period: xxxx
Tidally Locked: Y (where this only appears when Rotational_Period = 1)
Since the verbiage I am responding to was sloppy, specifically conflating Rotational Period and Rotational Speed, I feel the need to point out that the general concept of Rotational Speed is irrelevant to whether a body is Tidally Locked and only applies singly and locally to the relationship of a body in relationship to the body it is orbiting.