A consequence the gateway computed, and the token that proves it was shown.
The caller presents sessions (S13), and if the person accepts it sends confirmation straight back in a [WorkspaceLifecycleRequest]. The token is bound to this workspace, this action and this list, and it is spent by being used - so an acceptance is provably about the consequence that was on screen rather than one the caller says it displayed. ADR-267 recorded this as the recommendation; SP-8b's dialog is the round trip it was waiting for.
It is still not a credential. workspace.destroy is what authorizes the operation; this only says which question was answered. A token nobody can guess is not the point - a caller holding the scope could always mint its own before - the point is that the gateway and the dialog agree about what was accepted.
