AI & ML
Lineage Is Memory: Parent Inheritance and Feedback Disclosure in Short-Budget LLM-Guided Optimization
arXiv cs.SE0 views
arXiv:2610.41157v1 Announce Type: new Abstract: Iterative language-model optimizers refine prompts and programs by evaluating a candidate, showing a proposer model a sample of failing cases, and keeping revisions that improve performance. Recent work attributes the limits of this loop to narrow single-round reflection, introducing full-set error clustering, targeted minibatches, or larger proposer models so the optimizer sees more failure modes per step. Yet every existing evaluation tests these mechanisms exclusively inside lineage-preserving search, where each revision edits a surviving parent, leaving the contribution of parent inheritance confounded with the breadth of per-round feedback. Across 1,750 pre-registered runs spanning nine prompt and program synthesis benchmarks, we separate parent inheritance from feedback disclosure under matched evaluation budgets. We find that greedy parent inheritance drives the vast majority of optimization progress, outperforming seed-reset resampling even when seed-reset proposals receive a clustered summary of all failures in every round or use a larger proposer model. While full-set error clustering and diverse failure selection improve single-step rewrites from the seed and accelerate the opening rounds of search, sequential parent inheritance rapidly closes this gap as solved error modes are retained in the candidate and filtered from subsequent failure lists. Moreover, decomposing token expenditure in GEPA reveals that proposer reflection accounts for only a small fraction of total cost whereas validation and minibatch gating consume nearly the entire budget, showing that greedy parent inheritance over raw failures captures the gains of complex reflective loops at a fraction of their compute.
Source:https://arxiv.org/abs/2610.41157PreviousOne Verdict Is Not Enough: Regression Testing Learned World Models and Their Test HarnessesNextROSTrans: Empirically Benchmarking LLMs for ROS1-to-ROS2 Migration
Related posts
Federated AI Still Has a Central Coordinator Problem
0HackerNoon

The iPhone Duo has more than 100,000 optimized apps, Apple says
0The Verge
Product JSON-LD for WooCommerce: the fields AI shopping answers can actually use
0dev.to
It's a weird time to buy a laptop, but the new MacBook Pro doesn't skimp on quality
0Ars Technica
Could potential AI clones of GTA VI force a quicker official port?
0Ars Technica

AI is the new dating dealbreaker
0The Verge