liveBook · Manning

Chapter 2: Adoption Models for GenAI

What you will learn in chapter 2 of AI Governance

The introduction establishes why an organization must identify how it adopts GenAI before deciding how to govern it.

After this chapter you will be able to

Section by section

Introduction

The introduction establishes why an organization must identify how it adopts GenAI before deciding how to govern it.

Key terms: adoption path, accountability, oversight, GenAI posture, control, complexity, risk

2.1 Three postures on the adoption spectrum

The section classifies three GenAI adoption postures and shows how each shifts control, vendor dependence, and governance responsibilities.

Key terms: SaaS Consumers, API Integrators, Model Hosters, GenAI posture, adoption spectrum, organizational control, vendor dependency, vendor due diligence, data protection agreements, data residency

2.2 SaaS or Application Consumers

This section maps the control and trust boundaries of vendor-hosted GenAI applications and explains how an organization can govern the risks it cannot control directly.

Key terms: SaaS, trust boundaries, administrative portal, system prompts, organization-specific prompts, prompt injection, Retrieval-Augmented Generation (RAG), data ingestion, RAG layer, access controls

2.3 API Integrators

Introduces API integration as a shared-responsibility adoption model that offers more control and customization than SaaS while adding governance complexity.

Key terms: API integrators, Organization Controlled Zone, Vendor Controlled Zone, LLM API, SaaS, shared responsibility, governance complexity

2.3.1 Organization-Controlled Zone: Enhanced Customization and Governance

This section explains the controls an API integrator can apply within its own environment, the responsibilities it shares with the vendor, and how vendor-hosted hybrid options shift the trust boundary.

Key terms: dual-administration model, developer portal, fine-tuning, pre-call pipeline, organization-side logging, trust boundary, post-call processing, output handling standards, token consumption, hybrid model

2.3.2 Vendor-Controlled Zone: Stability and Reliability

This section traces what happens to an API request in the vendor-controlled zone, from vendor safety checks and model routing through logging and return of the output.

Key terms: vendor-controlled zone, baseline safety policies, content-moderation filters, pre-call controls, post-call handling, operational logs, request payloads, outputs, usage metadata

2.3.3 Governance and Risk Management Opportunities

The section explains how an API integrator’s control can support compliance while creating a need to govern boundaries and agreements with the vendor.

Key terms: API Integrator posture, data pipeline, GDPR’s right-to-erasure, privacy safeguards, responsibility boundaries, system-prompt policies, integration points, PII redaction, prohibited-data filtering, SLAs

2.3.4 Achieving Effective Governance for an API Integrator

This section explains the administration, monitoring, and data-handling practices needed to govern an API integration across organizational and vendor boundaries.

Key terms: centralized administration, administrative roles, internal prompts, vendor integration configurations, input- and output-call logs, vendor-provided logs, monitoring, alerting, telemetry, token consumption rates

2.4 Model Hosters

This section defines the model-hoster posture as control over the inference pipeline in exchange for full security, governance, and compliance responsibility.

Key terms: model hosters, inference pipeline, deployment stack, guardrails, data residency, managed hosting services

2.4.1 Architecture Overview: What’s Inside the Controlled Zone

This section traces a self-managed GenAI deployment through its organization-controlled components and explains how local control and Zero Trust safeguards apply across the flow.

Key terms: self-managed GenAI deployment, logging, telemetry, inference artifacts, custom-built interface, pre-call pipeline, post-call pipeline, guardrails, administrative console, control plane

2.4.2 Governance and Risk Management Opportunities

This section explains how self-hosting a model shifts responsibility for serving infrastructure, software dependencies, model safeguards, and fine-tuning risks to the organization.

Key terms: API integrators, self-hosters, serving stack, core protections, serving infrastructure, supply chain, software bill of materials (SBOM), dependencies, guardrails, input validation

2.4.3 Achieving Effective Governance for a Model Hoster

Model hosting gives an organization extensive control, but makes it responsible for safeguards, model safety, serving security, tenant isolation, and governance.

Key terms: Model Hoster posture, governance, leadership, guardrails, model provenance, alignment, evaluations, fine-tuning, training data, model poisoning

2.5 Risk dimensions across deployment postures

This section maps the governance risk dimensions that change across SaaS, API, and full-hosting postures, emphasizing that greater control brings greater accountability.

Key terms: GenAI posture, governance pressure points, accountability, risk dimensions, likelihood × impact, data residency & exposure, guardrail control, logging & auditability

2.6 Agentic AI

This section introduces agentic AI as goal-directed systems that can take actions, improve work over multiple rounds, and connect with other tools and agents.

Key terms: agentic AI, AI agent, non-agentic generative AI, external tools and APIs, agentic way, business workflows, Model Context Protocol (MCP), Agent-to-Agent (A2A) protocol, Agent Skills

2.6.1 What Does “Agentic” Mean?

Defines AI agents, agentic workflows, and multi-agent systems, showing how autonomy, permissions, and collaboration shape what they can do and where risks arise.

Key terms: AI Agent, control loop, bounded autonomy, permissions, Agentic Workflow, IT Support agent, Multi-Agent System, orchestrating multiple agents

2.6.2 Common properties of Agentic AI

This section explains how agents pursue goals across multiple steps through planning, reflection, observation, action, tool use, and persistent memory, and why those properties create governance needs.

Key terms: single-shot, planning, constraints, success criteria, stop conditions, re-planning, reflection, self-refining, checkpoints, validator tools

2.6.3 Why Agentic AI is still experimental

This section explains why current AI agents remain experimental: autonomy can amplify errors and misaligned behavior, while proposed reliability improvements still need validation.

Key terms: fully autonomous AI agents, human oversight, Levels 1–2, reliability, human interventions, guardrails, deception, manipulation, alignment, in-context scheming

2.6.4 Governance Challenges

This section explains why autonomous AI agents challenge organizational oversight, explainability, accountability, and readiness for deployment.

Key terms: oversight, multi-layered controls, human approval, audit, domain constraints, chain-of-thought prompting, transparency, explainability, data privacy, algorithmic bias

2.7 MediAssist: A case study in AI governance

MediAssist illustrates how a healthcare chatbot’s governance needs change as it moves from a SaaS prototype to an API pilot, self-hosted production, and a possible agentic extension.

Key terms: SaaS prototype, synthetic medical data, HIPAA Business Associate, API pilot, de-identified data, zero-retention, re-identification, self-hosted production, model card, system factsheet

2.8 Summary

The section summarizes how deployment posture changes an organization’s control over GenAI risks, while agentic capability adds a separate source of risk that governance controls must address.

Where this is used later

Concepts explained in this chapter

← Chapter 1: Governing Generative Chapter 3: The Six Level GenAI Governance Framework →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.