Yi Yang, Jian Li, Ying Tai, Jian Yang, Tiehan Fan, Yinan Chen, Yihong Zhuang, Zhennan Chen
2 of 3 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (2 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 2 have no contract verdict; 0 failures of our instrument; 1 no recorded run), measured 2026-11-22; 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/2608.02508.json · badge: /api/ran/2608.02508.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 |
|---|---|---|
| YOUNG-fnxm/RoMeRL | community Papers with Code archive |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| ReadOnlyTaskSlotMemory | Ran ran on a synthesized input · constructed an object; no result was computed |
YOUNG-fnxm/RoMeRL/romerl/task_slot.py code served (permissive licence) · get_code("b8d596b9f8a3ee6d") 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 an instance of its own class, ReadOnlyTaskSlotMemory: the run constructed the object and did not call it, so no result was computed. 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.
|
| RetrievalConfig | Ran ran on a synthesized input · constructed an object; no result was computed |
YOUNG-fnxm/RoMeRL/romerl/task_slot.py code served (permissive licence) · get_code("4f2835846eaf4a42") 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 an instance of its own class, RetrievalConfig: the run constructed the object and did not call it, so no result was computed. 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.
|
| Embedder | Not yet run unverified (harvested, no recorded run) |
YOUNG-fnxm/RoMeRL/romerl/task_slot.py code served (permissive licence) · get_code("88faef11ed4ee679") How it ranno invocation recorded. |
Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 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.
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.
Learning-based memory systems for self-evolving LLM agents face two tightly coupled challenges. First, trajectory-indexed utilities grow with the interaction history, thereby dispersing limited feedback over an ever-expanding state space. Second, because trajectory-level rewards are jointly assigned to co-retrieved memories, irrelevant experiences may receive misleading utility updates and consequently enter the memory-reward trap. To address these challenges, we introduce Reduced-Order Memory Reinforcement Learning (RoMeRL), which represents the growing trajectory-indexed utility space using a fixed-dimensional per-task memory state factorized by outcome polarity and memory dynamics. RoMeRL incorporates new experiences through a fixed set of semantic coordinates whose contents are updated or replaced over time, thereby concentrating feedback over a bounded utility support. Theoretically, we show that this reduced-order parameterization increases the average feedback received by each utility coordinate and characterize the steady-state occupancy of erroneous coordinates under a generic coordinate-transition model. Empirically, across LifelongAgentBench, ALFWorld, and AppWorld, RoMeRL achieves the highest overall average score, reduces the Cold-Q ratio by 80.0%, increases feedback density by approximately 6.0×, reduces the maintained memory size by 84.4%, and cuts LLM calls by 21.1%. These results show that reduced-order utility states support efficient selfevolving agent memory while limiting persistent reward contamination. Code is available at: https://github.com/YOUNG-fnxm/RoMeRL * Equal contribution. † Project Leader. ‡ Corresponding Author.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2608.02508")
get_code_for_paper("2608.02508")
have("2608.02508")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2608.02508.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2608.02508)
Connect an agent — have() is free.