8 of 8 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 3 have no contract verdict; 5 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2302.05328.json · badge: /api/ran/2302.05328.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| anzhang314/invcf | canonical (classifier label) classifier basis not recorded on the link |
8 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| clean | Ran ran on a synthesized input |
anzhang314/invcf/local_compile_setup.py code served (permissive licence) · get_code("92cd1d2e73d2a51b") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned function. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_extensions | Ran ran on a synthesized input |
anzhang314/invcf/local_compile_setup.py code served (permissive licence) · get_code("b870a0c9899a893a") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_include_dirs | Ran ran on a synthesized input |
anzhang314/invcf/local_compile_setup.py code served (permissive licence) · get_code("4443f98d2547d286") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| helper_load | Ran ran; our contract draft was wrong, not the code |
anzhang314/invcf/data.py pointer only (licence: MIT); the stored copy get_code serves, from lehengthu/alpharec, is pointer only (licence: NONE) · get_code("029327c4f6fb55d0") How it ranThe body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from lehengthu/alpharec, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| helper_load_train | Ran ran; our contract draft was wrong, not the code |
anzhang314/invcf/data.py pointer only (licence: MIT); the stored copy get_code serves, from lehengthu/alpharec, is pointer only (licence: NONE) · get_code("f1fe817c737b6fed") How it ranThe body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from lehengthu/alpharec, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| merge_user_list | Ran ran; our contract draft was wrong, not the code |
anzhang314/invcf/main_synthetic.py code served (permissive licence) · get_code("7513663e5a710c16") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned defaultdict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| merge_user_list_no_dup | Ran ran; our contract draft was wrong, not the code |
anzhang314/invcf/main_synthetic.py code served (permissive licence) · get_code("63bb511f56afa437") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned defaultdict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| save_checkpoint | Ran ran; our contract draft was wrong, not the code |
anzhang314/invcf/main_synthetic.py code served (permissive licence) · get_code("380a5cea5655f733") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
Of 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 8 distinct functions with an identity, 5 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 5 later) and 3 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| helper_load_train | 5 other papers 1 dated earlier, 4 later |
2210.11054 (2022-10) Incorporating Bias-aware Margins into Contrastive Loss for Collaborative Filtering |
2310.10108 (2023-10) On Generative Agents in Recommendation 2310.10696 (2023-10) Robust Collaborative Filtering to Popularity Distribution Shift and 2 more not named here |
| helper_load | 4 other papers 1 dated earlier, 3 later |
2210.11054 (2022-10) Incorporating Bias-aware Margins into Contrastive Loss for Collaborative Filtering |
2310.10108 (2023-10) On Generative Agents in Recommendation 2310.18700 (2023-10) Empowering Collaborative Filtering with Principled Adversarial Contrastive Loss and 1 more not named here |
| merge_user_list | 1 other paper 1 later |
2310.18700 (2023-10) Empowering Collaborative Filtering with Principled Adversarial Contrastive Loss |
|
| merge_user_list_no_dup | 1 other paper 1 later |
2310.18700 (2023-10) Empowering Collaborative Filtering with Principled Adversarial Contrastive Loss |
|
| save_checkpoint | 1 other paper 1 later |
2310.18700 (2023-10) Empowering Collaborative Filtering with Principled Adversarial Contrastive Loss |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Collaborative Filtering (CF) models, despite their great success, suffer from severe performance drops due to popularity distribution shifts, where these changes are ubiquitous and inevitable in real-world scenarios. Unfortunately, most leading popularity debiasing strategies, rather than tackling the vulnerability of CF models to varying popularity distributions, require prior knowledge of the test distribution to identify the degree of bias and further learn the popularity-entangled representations to mitigate the bias. Consequently, these models result in significant performance benefits in the target test set, while dramatically deviating the recommendation from users' true interests without knowing the popularity distribution in advance. In this work, we propose a novel learning framework, Invariant Collaborative Filtering (InvCF), to discover disentangled representations that faithfully reveal the latent preference and popularity semantics without making any assumption about the popularity distribution. At its core is the distillation of unbiased preference representations (i.e., user preference on item property), which are invariant to the change of popularity semantics, while filtering out the popularity feature that is unstable or outdated. Extensive experiments on five benchmark datasets and four evaluation settings (i.e., synthetic long-tail, unbiased, temporal split, and out-of-distribution evaluations) demonstrate that InvCF outperforms the state-of-the-art baselines in terms of popularity generalization ability on real recommendations. Visualization studies shed light on the advantages of InvCF for disentangled representation learning. Our codes are available at https://github.com/anzhang314/InvCF.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2302.05328")
get_code_for_paper("2302.05328")
have("2302.05328")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2302.05328.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2302.05328)
Connect an agent — have() is free.