A visual map of the paper’s central move: turn the improver into part of the editable system. The diagrams below focus on control-plane mutability, archive-driven search, memory as improvement substrate, and the difference between “better task behavior” versus “better future improvement machinery.”
Use the toggle to compare a conventional fixed meta-agent against a hyperagent where the improvement routine is editable too. The structure is the claim.
Step through the outer loop. The heatmap tracks which components are being revised over successive generations, while the ring diagram shows how memory and archive turn failed attempts into future search fuel.
Illustrative data only. The charts are designed to show the paper’s qualitative claim: editable improvement stays competitive in coding while helping transfer across less code-native tasks.
The paper’s practical tension is visible here: every new editable layer can raise capability and transfer, but it also enlarges the zone that must be logged, audited, and governed.