Line of inquiry
Inquiring lines›How does AI reshape human reasonin…›How do training data and procedure…›this line of inquiry
How should systems govern persistent agent-generated code in shared infrastructure?
A broader line of inquiry — a family of 13 specific questions the research asks around this. Follow one into its inquiring-line page, or move sideways to a related line below.
Questions in this line of inquiry 13
Specific inquiring lines the field asks around this — ordered from the most general framing down to the most specific angle.
- How do agents decide which created code deserves long-term persistence?
- How do agents decide which created code should persist versus disappear?
- Are durable shared code artifacts better than per-task harness patches?
- When should agent-created code be promoted into permanent harness infrastructure?
- How should human oversight apply to persistent agent-authored code?
- How do agent-created code artifacts become part of harness infrastructure?
- What makes persistent, shared code artifacts from agents hard to manage at scale?
- How should harness infrastructure validate code that agents generate themselves?
- Can one-off agent code be safely promoted to durable infrastructure?
- What makes agent-initiated artifacts the underexplored frontier in harness engineering?
- What prevents multiple agents from corrupting shared state in live artifacts?
- Why does forcing agents to trace function paths prevent unsupported claims?
- What lifecycle management prevents in-loop skill creation from bloating an agent?