UML25 — Location: p 373 outgoing_from_initial - Limitations on guards

The limitation on not having a guard seems not justified, if we can constrain that the set of guards are covering.
Please explain or fix.

The reason for not allowing a trigger on an initial transition is because that transition is triggered by the creation
and/or start behavior action of the state machine’s context object. That is, it is not triggered in the same way as other
transitions, by the arrival of amessage-based event occurrence. Putting a guard on this transition would allow for the
possibility that the transition would not be taken if the guard is false, leaving the state machine in an indeterminate
half-created state. (At that point, nothing further could be done with such a state machine, except to destroy it.) The
intent of this constraint, therefore, is to ensure that the initial transition is always taken.
Of course, the ability to branch following creation of the state machine is easily achieved by terminating the initial
transition on a choice point Pseudostate that has outgoing guarded transitions.
Disposition: Closed - No Change