跳到正文
研踪PaperTrail
← 研踪 PaperTrail

arXiv:2608.10450 · v4

Persistent Recursive Worlds Enable Autonomous Software Evolution

首次提交 2026-08-11 12:04
版本更新 2026-11-17 11:48
雷达观测 2026-11-18 19:43
arXiv ↗PDF ↗

摘要

Software systems accumulate dependencies and design commitments over time, while the agents that modify them operate within bounded sessions. How, then, can development remain cumulative across generations of transient agents? We introduce EvoX Genesis, which organizes development as a persistent recursive software world. Agents enter an accepted repository version, delegate work within local scopes, and submit changes for verification and parent review. Once accepted, those changes pass to later episodes together with the contracts and tests used to assess them. The project thus preserves both earlier work and a basis for evaluating what comes next. We examine this continuity through four studies of formation, continuation and redevelopment. Starting without compiler code, Genesis built a C compiler with 219,676 lines of Rust source through 1,019 agent episodes over 123.4 hours. Within this growing implementation, repairs increased passes on a fixed set of 100 Csmith programs from 61 to 93; a subsequent revision retained all 93 passes. Development also continued in a separate compiler lineage when DeepSeek V4 Flash inherited a GLM 5.2 snapshot. To examine continuity when the implementation itself changes, Genesis redeveloped selected MESA functionality in Rust, with numerical agreement assessed against the Fortran reference across six workloads. The WebGL trajectory, meanwhile, exposed both repairs and regressions as repeated checks recorded progress towards 2,017/2,019 conformance pages passed. A complementary EvoX Compiler case connects program-merging performance to executable graph and backend contracts. Together, these records trace how accepted work becomes a foundation for further development: later agents inherit both usable implementations and concrete ways to assess further revisions.

AI 论文解读

基于摘要 · 非全文审阅

此版本尚未生成 AI 解读。解读由后台任务生成并按论文版本保存,登录后共享已有结果。

版本差异

本站首次收录为 v4,暂无更早版本可对照。

观测到的版本

相邻记录可能跳过中间版本;首次发现 v2 及以上也会标为版本更新。

v4 · 2026-11-17 11:48 · 最新观测版本

Persistent Recursive Worlds Enable Autonomous Software Evolution

Software systems accumulate dependencies and design commitments over time, while the agents that modify them operate within bounded sessions. How, then, can development remain cumulative across generations of transient agents? We introduce EvoX Genesis, which organizes development as a persistent recursive software world. Agents enter an accepted repository version, delegate work within local scopes, and submit changes for verification and parent review. Once accepted, those changes pass to later episodes together with the contracts and tests used to assess them. The project thus preserves both earlier work and a basis for evaluating what comes next. We examine this continuity through four studies of formation, continuation and redevelopment. Starting without compiler code, Genesis built a C compiler with 219,676 lines of Rust source through 1,019 agent episodes over 123.4 hours. Within this growing implementation, repairs increased passes on a fixed set of 100 Csmith programs from 61 to 93; a subsequent revision retained all 93 passes. Development also continued in a separate compiler lineage when DeepSeek V4 Flash inherited a GLM 5.2 snapshot. To examine continuity when the implementation itself changes, Genesis redeveloped selected MESA functionality in Rust, with numerical agreement assessed against the Fortran reference across six workloads. The WebGL trajectory, meanwhile, exposed both repairs and regressions as repeated checks recorded progress towards 2,017/2,019 conformance pages passed. A complementary EvoX Compiler case connects program-merging performance to executable graph and backend contracts. Together, these records trace how accepted work becomes a foundation for further development: later agents inherit both usable implementations and concrete ways to assess further revisions.

查看此版本解读 →查看此版本原文 ↗