Expose the alternatives and obligations that the selected commitment really has. An established prerequisite should not become an avoidable flag or optional value that every leaf must rediscover. Genuine runtime alternatives remain explicit and can lead to protected continuations.
Why: a simple-looking interface can conceal uncertainty and encourage unsafe retries. An excessively general interface can burden every consumer with outcomes that its operation cannot have.
Consequence: a known pending operation, an unknown result, an applied effect and a failed view refresh are different facts. Recording a rejection can be a successful review; refusing an unauthorized review is another outcome. A pure label formatter may remain total. There is no universal outcome enum.
Moves restrict local reuse. They do not establish completion, crash durability, external truth or distributed exactly-once effects. Outstanding work needs an owner and a survival mechanism for the boundary promised. A browser presents server-owned outcomes; a cached action or serialized receipt is not current server authority.