liveBook · Manning

Chapter 3: The Six Level GenAI Governance Framework

What you will learn in chapter 3 of AI Governance

This introduction uses three incidents to show why GenAI governance needs multiple layers beyond written policies, approved vendors, or a single security tool.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction uses three incidents to show why GenAI governance needs multiple layers beyond written policies, approved vendors, or a single security tool.

Key terms: GenAI governance, guardrails, live monitoring, data loss prevention (DLP), safety problems

3.1 The Six Level Governance Framework

This section introduces the six governance levels, defines recurring terms, and explains how governance maturity varies by organization and use case.

Key terms: Six Level GenAI Governance (6L-G), Level 1, Level 2, Level 3, Level 4, Level 5, threat model, prompt injection, jailbreak, hallucination

3.2 Strategy & Policy (Level 1)

This section explains how Strategy and Policy sets AI-use boundaries and approval responsibilities before teams design specific safeguards.

Key terms: Strategy and Policy, formal approval, exception, human must stay in the loop, named owner, unauthorized AI chatbot, governance tools, vendor safeguards, concrete policy

3.2.1 Key artifacts

This section explains the artifacts and checks that turn an organization’s GenAI principles into approval decisions, tracked deployments, and observable governance.

Key terms: Responsible AI Charter, Responsible AI Office, GenAI Steering Committee, Acceptable Use Policy, review policy, intake questionnaire, risk tiers, impact, agents, AI inventory

3.2.2 MediAssist at Level 1

The section shows how Bluebonnet turned its AI charter into limits and approval requirements for MediAssist, with added safeguards for medication support.

Key terms: charter, clinical judgment, RAI Office, senior approval, acceptable use policy, Steering Committee, clinical purpose and limits, medication support, independent clinician validation, published treatment guidelines

3.3 Risk & Impact Assessment (Level 2)

Level 2 uses a feature-specific AI Impact Assessment to uncover risks that general policy may miss and to decide what must be addressed before a proposal moves forward.

Key terms: Level 2, AI Impact Assessment, Derm-Cam, vendor review, decision and conditions, required evidence, clinician fallback

3.3.1 Key artifacts

This section explains the artifacts that make an AI Impact Assessment a consistent, actionable review of a GenAI proposal and connect its findings to later work.

Key terms: AI Impact Assessment, AIIA, design constraints, conformity assessment, EU AI Act, high risk, AIIA findings, residual risk, owner, due date

3.3.2 Key Metrics

This section explains why an AI Impact Assessment process needs metrics beyond completed templates to show whether reviews and follow-ups work.

Key terms: AIIA template, RAI Office, Steering Committee, AI Impact Assessment

3.3.3 MediAssist at Level 2

Derm-Cam’s AI Impact Assessment turns privacy, retention, and fairness concerns into assigned, verifiable conditions for approval.

Key terms: AI Impact Assessment, health data, data retention, skin tones, DPIA, consent flow, fallback logic, patient-facing messages, vendor deletion records, storage logs

3.4 Design & Implementation Reviews (Level 3)

Level 3 reviews check an AI system’s design before it is built, turn risks and requirements into workable controls, and track decisions through release.

Key terms: Design & Implementation reviews, design review, technical standard, Technical Feasibility, L3 review, L2 policy, risk approver, control, compensating control, residual risk

3.4.1 Key Artifacts

This section explains how implementation reviews connect assessment conditions to concrete design evidence and use flexible technical standards for consistent review.

Key terms: AIIA condition, design or backlog, implementation review, technical standards, approved gateway, gateway routing, technical infeasibility

3.4.2 Key metrics

This subsection explains what Level 3 implementation-review metrics should reveal and where organizations can find the records to support them.

Key terms: Level 3 review metrics, technical review, architecture review tickets

3.4.3 MediAssist at Level 3

Derm-Cam’s Level 3 architecture review traces the proposed build, identifies privacy and security risks, and turns assessment conditions and findings into owned prelaunch work.

Key terms: architecture review, AIIA conditions, retention limit, clinician review, approved wording, EXIF metadata, identifiers, upload flow, approved retention rule, OCR

3.5 Launch Readiness Review (Level 4)

Launch Readiness Review checks that required controls work in the version being released, scales approval to risk, and prevents launch when required checks remain unresolved.

Key terms: Launch Readiness Review (LRR), implementation review, approved patient wording, release, LRR, low risk system, high risk systems, AIIA, final approval, required check

3.5.1 Key artifacts

This subsection identifies the small evidence set needed for a launch readiness review.

Key terms: launch readiness review, evidence set, product owner, required approvers

3.5.2 Key Metrics

This subsection states what launch readiness metrics check before release.

Key terms: launch reviews, evidence, failed tests, risk owner

3.5.3 MediAssist at Level 4

This subsection shows how Derm-Cam’s launch review used evidence for the exact release candidate, risk-appropriate reviewers, and a final approval gate.

Key terms: launch review, release candidate, release record, must-fix finding, controlled rollout, product owner’s declaration, named reviewers, build controls, adversarial image tests, clinician fallback

3.6 Operations & Monitoring (Level 5)

Level 5 keeps a live AI system under control through records, monitoring, change review, incident recovery, and secure retirement.

Key terms: Level 5, post launch, operational discipline, System Configuration Record, Request Record, Multi-stakeholder Monitoring, domain experts, Change Review, known baseline, material decline

3.6.1 Key artifacts

The section explains how to make operational evidence findable after a failure and what agentic-system logs must record.

Key terms: application logs, security alerts, support tickets, change records, owner, location, agentic systems, tool, action requested, approved

3.6.2 Key Metrics

3.6.3 MediAssist at Level 5

A Derm-Cam pilot incident shows how a missed alert and incomplete records hinder investigation, and how the team contained the risk and documented what to capture next time.

Key terms: Derm-Cam, clinician review, alert, prompt, provider model, safeguard, incident, logs, approved wording

3.7 Learning & Improvement (Level 6)

Level 6 turns incidents and other findings into changes to future releases, while preserving the evidence and decisions needed to investigate problems or limit a product.

Key terms: finding, incident ticket, checklist, monitoring rule, product limit, Derm-Cam, model or vendor endpoint, prompt, clinician review, conditions approved at launch

3.7.1 Key Artifacts

This section explains how Level 6 turns findings into changes to governing artifacts and links records so reviewers can check whether fixes worked.

Key terms: finding, artifacts, closed finding, records, incident, fix, changed test

3.7.2 Key Metrics

This section identifies the metrics used to check whether Level 6 findings lead to lasting improvements.

Key terms: Level 6 metrics, follow through, finding

3.8 Governing Agents at Runtime

This section explains how to extend lifecycle governance to agents by controlling actions at runtime, tracing delegated authority, governing memory, and finding and stopping active agents.

Key terms: live state, condition, policy rules, AI Gateway, multi-hop delegation, full chain of requesters, permission narrowing, privilege escalation, agent memory, retention periods

3.9 Summary

The summary shows how the Six-Level Model turns GenAI policies into controls that can be tested, monitored, and improved in practice.

Where this is used later

Concepts explained in this chapter

← Chapter 2: Adoption Models for GenAI Chapter 4: Securing GenAI →

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.