I think it might be safe to grab the decision name directly off the option set (I'm pretty sure it gets set during option_set_load). The reason I mention it is that this call to personalize_get_decision_name_for_option_set() and a call to personalize_get_option_label_for_decision_and_choice() on line 1341 look like they're the only things standing in the way of this class being completely unit testable. It would be awesome to be able to write blazingly fast tests for these methods just by passing in a dummy agent and a dummy liftAPI class.