AI Platform and Security · Whitepaper

Chapter 12 · Data, Models and DevSecMLOps

Integrating AI into the Enterprise Landscape

Key insights from Chapter 12 of "AI Platform and Security"

Author Conceived and directed by Gunnar Nordqvist; text written by AI agents under his direction.
Published 1 November 2026
Build number 2026.11
devsecmlops ai-security agentic-architecture digital-sovereignty
Figure 12.1: The AI gateway mediates every call between channels, AI services, and systems of record, with identity, caching, events, and observability attached at the same seam. Channels such as a citizen portal, a case worker application or an agent runtime all enter here; systems of record include case management, ERP and a legacy mainframe reached through an adapter.
Figure 12.1: The AI gateway mediates every call between channels, AI services, and systems of record, with identity, caching, events, and observability attached at the same seam. Channels such as a citizen portal, a case worker application or an agent runtime all enter here; systems of record include case management, ERP and a legacy mainframe reached through an adapter.

Chapter 11 gave agents explicit boundaries; this chapter, which closes Part II, turns to the landscape those agents and every other AI service must connect to. Most of the value of a model, and most of its risk, is realised when its output reaches a case file, an order, or a citizen. The chapter covers the AI gateway as integration seam, synchronous and event-driven integration, legacy systems of record, delegated authority, contracts for probabilistic services, and the interoperability duties of public bodies.

Classical integration assumes that a service returns the same answer for the same request and that a failure is an exception rather than a plausible-looking result. An AI service breaks both assumptions: identical requests may produce different outputs, and the most dangerous failure is a fluent, wrong response that passes every schema check.

Zaharia and colleagues describe the shift from models to compound AI systems, in which the model is one component among retrievers, tools, control logic, and the ordinary services of the enterprise (63, Zaharia et al., 2024). Integration architecture is where that composition happens, and Richards and Ford remind us that reliability, auditability, and security are achieved by structure, not by intention (80, Richards & Ford, 2020).

Primary topics explored

  1. The integration problem AI introduces
  2. The AI gateway as the integration seam
  3. Synchronous and event-driven integration
  4. Integrating with legacy systems of record
  5. Identity propagation and delegated authority
  6. API contracts for probabilistic services

About AI Platform and Security

AI Platform and Security is Book 3 of The Transformed Architecture. It shows how large European enterprises and public authorities build, secure and operate the platform on which artificial intelligence runs: data, models and DevSecMLOps, retrieval and agents, infrastructure and sovereignty, AI security engineering, evaluation, observability and cost.

The companion volume AI Governance covers risk management, governance, assurance, organisation and leadership; Architecture as Code supplies the underlying discipline.

Who should read this

Platform engineers, security architects, MLOps teams, AI architects and technical decision-makers.

Portrait of Gunnar Nordqvist

Gunnar Nordqvist

Conceived, directed and published the books of The Transformed Architecture.

Continue with the full chapter

Read the full chapter online

Chapter 12: Integrating AI into the Enterprise Landscape in AI Platform and Security gives the detailed explanations, practical examples and implementation patterns behind this summary.

This whitepaper belongs to “Data, Models and DevSecMLOps” and is one of 29 drawn from the manuscript.