This is an old revision of the document!
All Roles should be bound as an atomic operation before an Interaction starts, which leaves no place for unbound Roles. If you run into that problem, it could be a sign that the scope of the Context is too large, or other problems with the underlying mental model.
Note the difference between “unbound Roles” and “Roles set to null”. Setting the field that identifies a Role to null is allowed if your language supports it, be aware though that it can complicate things, forcing null checks throughout the Context.
Also note that the Roles can all be rebound before another Interaction in the same Context occurs.