Skip to content
Open access

From DevOps to XOps: an agent-driven reference architecture for autonomous enterprise operations

Sep 2026 · Scientific Reports · 0 citations

TL;DR

XOps is proposed, a five-layer reference architecture integrating PlatformOps, DataOps, MLOps and AIOps beneath an Agentic Orchestration layer with Policy-as-Code governance, together with a continuous-time Markov chain model quantifying the availability effect of agent-driven remediation.

Abstract

Enterprise adoption of machine learning has fragmented operations into specialised disciplines—DataOps, MLOps, AIOps—creating silos that impede unified governance. We propose XOps, a five-layer reference architecture integrating PlatformOps, DataOps, MLOps and AIOps beneath an Agentic Orchestration layer with Policy-as-Code governance, together with a continuous-time Markov chain model quantifying the availability effect of agent-driven remediation. Two case studies evaluate the architecture under controlled, synthetic conditions. For a self-healing payment gateway, 250 live executions of the reasoning graph against a hosted language model and a live policy engine yield 85.6% plan-level action consistency and 99.6% fault classification accuracy, with 12.4% of plans rejected by the policy gate and escalated to a human and no policy-violating action authorised for execution; the pipeline’s 3.3-minute recovery time is a simulated latency budget rather than a cluster measurement. For a predictive-maintenance application on NASA C-MAPSS data, autonomous drift detection and retraining sustain $$R^2 = 0.74$$ against 0.29 for an equivalent static model, measured on engines reserved entirely from retraining. An indicative cost analysis suggests an approximately 70% reduction in expected monthly operational cost. Within this scope the results support the feasibility of agent-driven operations rather than establishing production-scale performance.

Read PDF

Similar papers

Conference Aug 2026

Architectural Patterns for Scalable Multi-Agent LLM Systems: A Software Engineering Perspective

The proliferation of large language model (LLM)-based autonomous agents has created a new class of distributed system: the multi-agent LLM network. While significant research focuses on the intelligence of individual agents, comparatively little work addresses the software architectural concerns that govern how fleets...

Ketankumar Savajiyani · 0 citations
Sep 2026

Agentic FinOps: An Autonomous Framework for Real-Time Cost Governance in AI-Infused Cloud Architectures

As enterprises scale Generative AI from experimental pilots to mission critical production, cloud expenditures have shifted toward volatile, token based and GPU intensive consumption models. Traditional reactive FinOps frameworks fail to address the nonlinear cost dynamics of large language models (LLMs) and distribute...

Sandip Patel, Prakash Upadhyay, Sibasis Padhi · 0 citations
Review Open access Aug 2026

AI-Assisted Test Execution as an Augmentation Layer in Enterprise Quality Engineering

The Probabilistic Augmentation and Governance Model (PAGM), a three-tier framework that formally allocates responsibility between AI agents and human testers across autonomous execution, confidence-gated escalation, and human-led verification, provides a governance-ready foundation for organizations seeking to deploy A...

Rejenish Kiran · 0 citations
Conference Aug 2026

LLMOps at Scale: Reliability, Cost Governance, and Multi-Model Orchestration for Enterprise Generative AI Platforms

Enterprise deployments of large language models (LLMs) expose a class of operational challenges that differ fundamentally from classical machine-learning services: probabilistic outputs, prompt sensitivity, token-based costs that scale with request volume, multi-provider availability variability, and the absence of a s...

Rajesh Balaji · 0 citations
#artificial intelligence Review Sep 2026

Maat: Independent Deterministic Contract-Based Governance for Multi-Agent LLM Workflows

Maat is presented, a runtime governance layer that validates agent-to-agent handoffs against a versioned workflow contract, or anchor, with no language model in the validation or scoring path and the results support deterministic handoff validation for contract-expressible defects.

Uliana Elina · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.