UMLR — Shouldn't it be possible to make the state of an object be private to support encapsulation/information hiding?.

From the following
"A guard constraint may involve tests of orthogonal States of the current StateMachine, or explicitly designated States of some reachable object"

it appears, that no matter how reachable object is defined (see UMLR-402), if it is reachable, the state is accessible. This seems to go against the principles of encapsulation and information hiding. We can make all the attribute of an object private, but the state, which is a often defined by the values of the attributes can't be made private

My age may be private, but the fact that I'm in the state of being a teenage must be public? <wishful thinking perhaps>

There should be some way of making an object's state private.