Forward-Deployed Full-Stack Engineering for Autonomous Cloud MLOps
Not on the map. Why?
Abstract (arXiv)
Across industries, machine-learning systems support applications ranging from prediction and anomaly detection to forecasting, optimization, and scheduling, yet operationalizing these systems requires coordinating application development, model pipelines, cloud infrastructure, security, deployment, monitoring, retraining, recovery, and rollback. We present an evidence-gated multi-agent framework for transforming a natural-language MLOps cloud engineering task into a verified repository and operational cloud deployment. The framework combines graph engineering, loop engineering, and agent harness engineering. A stateful Graph Orchestrator coordinates specialized agents for repository generation, review, execution, verification, release, and monitoring while governing workflow dependencies, evidence gates, retry bounds, recovery paths, and termination. Consequential lifecycle transitions proceed only when their required predicates are supported by verifiable execution or runtime evidence. Verification failures activate bounded reflection, repair, and re-verification, while runtime evidence of failure, drift, degradation, or policy violation can trigger bounded adaptation, recovery, or rollback. Agent harness engineering constrains repository generation, review, and repair, artifact execution, and cloud operations through controlled capabilities and isolated execution environments. We realize the framework on Google Cloud Platform and evaluate repository completeness, controlled execution, evidence-gated transitions, cloud promotion, and bounded recovery. Our experimental results show that the framework prevents unsupported lifecycle transitions and drives each run toward either a verified operational deployment or an auditable terminal failure.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 23 of its 33 references that are in the map. First posted on arXiv 30 Aug 2026.
Builds on
23 of 33 references.
References · 23
- 2022ReAct: Synergizing Reasoning and Acting in Language Modelscited by 8,695
- 2023Reflexion: Language Agents with Verbal Reinforcement Learningcited by 4,276
- 2023MetaGPT: Meta Programming for A Multi-Agent Collaborative Frameworkcited by 1,808
- 2024SWE-agent: Agent-Computer Interfaces Enable Automated Software Engineeringcited by 1,737
- 2023CRITIC: Large Language Models Can Self-Correct with Tool-Interactive Critiquingcited by 783
- 2024AFlow: Automating Agentic Workflow Generationcited by 432
- 2025Agentic Context Engineering: Evolving Contexts for Self-Improving Language Modelscited by 398
- 2026Agentic Harness Engineering: Observability-Driven Automatic Evolution of Coding-Agent Harnessescited by 142
- 2022Machine Learning Operations (MLOps): Overview, Definition, and Architecturecited by 128
- 2024Language Agents as Optimizable Graphscited by 89
- 2025NL2Repo-Bench: Towards Long-Horizon Repository Generation Evaluation of Coding Agentscited by 65
- 2026Towards a Science of AI Agent Reliabilitycited by 65
11 more
- 2025Agentic Software Engineering: Foundational Pillars and a Research Roadmapcited by 41
- 2026From Agent Traces to Trust: A Survey of Evidence Tracing and Execution Provenance in LLM Agentscited by 37
- 2026From Static Templates to Dynamic Runtime Graphs: A Survey of Workflow Optimization for LLM Agentscited by 24
- 2026AI Harness Engineering: A Runtime Substrate for Foundation-Model Software Agentscited by 20
- 2026RepoZero: Can LLMs Generate a Code Repository from Scratch?cited by 14
- 2026Time to REFLECT: Can We Trust LLM Judges for Evidence-based Research Agents?cited by 10
- 2025Beyond Task Completion: An Assessment Framework for Evaluating Agentic AI Systemscited by 8
- 2026Stop Hand-Holding Your Coding Agent: Engineering the Loops that Replace Step-by-Step Promptingcited by 5
- 2026Human-on-the-Bridge: Scalable Evaluation for AI Agentscited by 4
- 2026AgentS4D: Benchmarking Runtime Risks across the Execution Lifecycle of LLM-Based Workspace Agentscited by 3
- 2026What makes prompts a graph: necessary and sufficient conditions for prompt graph engineeringcited by 1
Built on by
Not cited yet.