- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
MOGR generates a task token before each item's semantic ID, allowing one decoder to serve several objectives. Objective-Conditioned Distillation transfers objective-specific teachers into this decoder; LGPO updates list composition using online feedback. An additional tokenizer, OBRQ, incorporates objective-specific collaborative embeddings. Evaluation covers Kwai26 retrieval, an offline reward-model proxy, industrial codebook comparisons, and live A/B tests.
Critical strengths
- The online comparison addresses an important confound. Beyond comparing against greedy OCD, Table 7 includes frozen OCD with identical exploration. LGPO still improves Read/Poi/Int by 0.254%/0.218%/0.269%. This supports a benefit from learning beyond changing the exploration policy.
- Distillation improves all three offline objectives. In Table 1, removing OCD reduces Long-View/Like/Forward Recall@512 from 0.193/0.139/0.145 to 0.175/0.127/0.140. Table 6 also compares the student and teachers under forced objective tokens, making the transfer effect more directly observable.
Critical weaknesses
- LGPO's update is only partially aligned with its serving process. Advantages compare consecutive requests with changing histories, while the clipped ratio covers only one sampled task token. Other task tokens and SIDs are decoded greedily, and shared parameters continue to change. The paper acknowledges that this is not the full serving-policy ratio. The A/B supports the implemented procedure, but does not establish that the update cleanly attributes reward differences to objective placement rather than changing request states.
- The tokenizer results do not isolate exact-item retrieval. The evaluation accepts a gold-item or SID match, and Table 8 reports collisions under every industrial codebook. Because changing the codebook also changes item equivalence under this hit rule, Table 5 alone cannot determine how much of OBRQ's improvement survives exact-item scoring.
Questions for authors
- Clarification: What are the request-time spans and history changes within the online groups? Is there evidence that the reported gain is robust to the resulting within-user state variation, beyond changing group size in Figure 5?
- Evaluation clarification: For Table 5, how many hits match only the target SID rather than the target item, and do the codebook gains persist when these are separated?
Discussion encouraged during this period!
Hi all reviewers,
We’re about halfway through the discussion period. This is a friendly reminder to check the authors' replies. If the authors have answered questions or responded to critiques in the reviews, please leave a comment for the authors!
Thank you so much!
Best, Your AC