PIANO: personalized music reranking with an information aggregation node¶
Fidelity: core mechanism. Runs the defining mechanism verifiable on public data. Private data, production models, and serving remain outside scope.
Paper information¶
| Field | Details |
|---|---|
| Paper | arXiv 2606.16641 |
| Organization | NetEase Cloud Music |
| First public release | 2026-06-15 (arXiv v1) |
| Authors' code | The paper did not provide official or author code when checked on 2026-09-02. |
| Adapter / method | piano |
| Local reproduction code | src/auto_research/reproductions/piano/ |
Original paper¶
Motivation and method¶
The Query-Driven Interest Refiner extracts query-relevant interests from history. The Information Aggregation Node summarizes the entire candidate list and conditions item-level CTR/CVR predictions.
flowchart LR
A["Public behavior and candidates"] --> B["PIANO core mechanism"]
B --> C["Matched-budget method output"]
A --> D["Paper-defined direct baseline"]
C --> E["Common metrics and structural diagnostics"]
D --> E
Key figure from the paper¶
Figure 1: Core architecture, modules, and connections. From the original paper; copyright remains with the authors.
Core equations¶
Paper results¶
Stable multi-week traffic assignments at NetEase Cloud Music yield CTR +0.62% and CVR +4.45% in A/B, followed by rollout to 95% of traffic. This is paper evidence, not a local public-data outcome.
Local reproduction¶
Local comparison: Under the same full-catalog protocol, baseline NDCG@10 is 0.05401 and PIANO NDCG@10 is 0.04988, -7.65% relative, a negative proxy result. The local proxy does not extrapolate to online lift.
See the three-seed artifact for complete results, means, standard deviations, and 95% confidence intervals.
Reproduction boundaries¶
The local run uses a public MovieLens-1M subset and auditable proxies to validate the core computation. It does not reproduce private logs, production models, online traffic assignment, or serving. No claim is made to reproduce absolute paper metrics or online gains.
