Agree, this is the point the article makes. I don't think the article claims that it's the agent that is directly improved or altered, but that through the proc

Agree, this is the point the article makes. I don't think the article claims that it's the agent that is directly improved or altered, but that through the process of the agent self-maintaining its environment, then using that improvement to bootstrap its future self or sub-agents, that the agent _performance_ is holistically better. > ... if the docs act like a summary of current state, you can just read it at the start and update it at the end of a session Yeah, exactly. The documentation is effectively a compressed version of the code, saving agent context for a good cross-section of (a) the big picture, and (b) the details needed to implement a given change to the system. Think we're all on the same page here, but maybe framing it differently.