In brief
The challenge. Long-running AI research programmes often stall on manual iteration. Hyperparameter tuning, disconnected tooling and poorly scheduled execution slow engineers and leave costly compute idle.
The response. Continuous model improvement needs a governed, closed loop that can propose, run, evaluate and record experiments without requiring an engineer to manage every step.
What this paper covers. This paper describes an architecture for automated reinforcement learning (RL) experiments. LLMs propose code changes; fixed evaluation criteria and deterministic version control keep each iteration measurable and auditable.
The automation of model improvement
Manual hyperparameter tuning and fragmented execution limit the pace of AI research and leave expensive compute underused. An autonomous RL research system can address these constraints through four operational components.
Two trends support the case for automation. Stanford HAI's 2025 AI Index reports that training compute for notable AI models is doubling approximately every five months. It also reports that the cost of GPT-3.5-level inference fell more than 280-fold, from $20.00 to $0.07 per million tokens. Greater model complexity increases the burden of experimentation, while cheaper inference reduces the cost of using LLMs to manage it.
Early systems show what this approach can achieve. Google DeepMind reports that AlphaEvolve improved a matrix multiplication kernel in Gemini's architecture by 23% and recovered an average of 0.7% of Google's worldwide compute resources through a scheduling heuristic. Sakana AI's AI Scientist demonstrated an automated workflow from idea generation to reviewed manuscript for less than $15 per paper. These examples establish technical feasibility, although they do not by themselves prove that every research workload will deliver the same economic benefit.
| Operational pillar | Technical mechanism | Strategic enterprise impact |
|---|---|---|
| LLM-Guided Iteration | An LLM proposes hyperparameter changes or specific code diffs. | Reduces the engineering time needed to formulate and configure experiments. |
| Distributed Execution | Training runs are routed to local or cloud GPU targets. | Matches workload requirements to available capacity and cost. |
| Governed Quality Control | Each result is evaluated against fixed criteria; weak runs are rejected. | Helps detect regressions and makes improvement claims comparable across runs. |
| State Management | The system supports checkpointing, resumption and versioned retention. | Provides an auditable lineage for both retained and rejected experiments. |
Reference architecture: the autonomous experimentation fabric
The reference architecture separates proposal, execution and governance. Together, these layers allow experiments to be generated, run, measured and recorded continuously, while keeping human approval at defined control points.
2.1The proposal & orchestration engine
LLM-guided experiment loops
An orchestration layer uses a designated reasoning model to analyse previous failures and propose hyperparameter changes or architectural code diffs.
Hyperparameter search
Grid and Bayesian search explore the optimisation space within defined parameters.
2.2The execution & evaluation layer
Hybrid GPU targets
The orchestration engine sends proposed training runs to local bare-metal clusters or cloud GPU instances according to capacity and cost constraints.
Frozen evaluation boundary
After each run, the candidate model is benchmarked against a fixed dataset and predefined criteria. This reduces evaluation drift and makes results comparable.
2.3The governance & versioning ledger
Checkpointing
Automated checkpointing and resumption allow long-running training loops to recover from hardware pre-emption or spot-instance termination.
Traceable lineage
Rejected runs are logged for negative-result analysis; successful iterations are retained as traceable versions in the enterprise model registry.
Engineering implementation roadmap
Deployment should proceed in three phases. Evaluation controls and state management come first, followed by the LLM proposal engine and, finally, closed-loop automation.
Foundation & Guardrails
- Frozen evaluation boundary
- Target compute mapping
- Checkpoint configuration
The LLM Engine
- LLM proposal integration
- Hyperparameter search
- Code-diff generation
Closed-Loop Automation
- Automated execution
- Result evaluation
- Traceable versioning
- Establishing guardrails. Define the immutable evaluation datasets and configure the routing logic for local or cloud GPU targets.
- Integrating the engine. Deploy the LLM-guided loops responsible for generating hyperparameter and code-diff search parameters.
- Closing the loop. Automate execution and evaluation, reject weak runs, and promote only traceable versions that meet the agreed criteria.
How Setloop can help
Closed-loop reinforcement learning depends on research engineering, evaluation design, infrastructure automation and GPU operations. Setloop brings these disciplines together to build systems that can move from controlled experiments into production workflows.
Bespoke research automation
Setloop provides Automatic RL Research as a consultancy service for AI teams running long-term research programmes.
Working infrastructure over slide decks
Setloop builds the experiment loop, evaluation controls and supporting infrastructure within the customer's private or cloud environment.
End-to-end GPU execution
Setloop can integrate these research loops with GPU workload planning so experiments run on infrastructure selected for capacity, performance and cost.
What research and infrastructure leaders should remember
- Manual iteration limits scale. Long-running research programmes need more than manual hyperparameter tuning and disconnected execution.
- Evaluation criteria must remain stable. A fixed dataset and predefined measures reduce drift and make results comparable across iterations.
- Every run must be auditable. Record both retained and rejected experiments so that decisions, failures and model lineage can be examined later.
- Autonomous loops must run on cost-accountable infrastructure. Routing training runs across local bare-metal and cloud GPU targets by capacity and cost keeps continuous experimentation economically sustainable.
References
- Stanford HAI. “AI Index Report 2025.” Stanford University, April 2025.
- Google DeepMind. “AlphaEvolve: A Gemini-powered coding agent for designing advanced algorithms.” May 2025.
- Lu, C. et al. “The AI Scientist: Towards Fully Automated Open-Ended Scientific Discovery.” arXiv:2408.06292, August 2024.
- MarketsandMarkets. “Automated Machine Learning (AutoML) Market: Global Forecast to 2028.” 2023.
- ClearML, AI Infrastructure Alliance, and FuriosaAI. “The State of AI Infrastructure at Scale 2024.” March 2024.
About Setloop
Setloop is an engineering consultancy and product studio for organisations building GPU workloads, cloud GPU platforms, private AI infrastructure and AI factory architectures. Its engineers design, benchmark and deploy operational infrastructure in customers' private and hybrid-cloud environments across the UK and EU.
The Setloop Technical White Paper Series distils reference architectures from client work and the Setloop product portfolio, including LLMTrace, AutoOps, GPU Cloud Platform, AI FinOps and Automatic RL Research.
- Web: setloop.io
- Email: [email protected]
- LinkedIn: /company/setloop
- Book a GPU architecture review: setloop.io/contact