How to Use This Book

The Callout Box System

This book uses a consistent set of visual markers to signal different types of content. Learn to recognize them and you will be able to navigate each chapter more efficiently.

Reading Paths

You do not have to read this book from front to back. Depending on your role and goals, one of these paths may serve you better.

Path 1: The Sequential Learner

Who: Students, career-changers entering compliance, professionals who prefer to build knowledge systematically. Route: Chapters 1–40 in order. Read exercises and case studies. Complete at least one capstone project.

Path 2: The Compliance Practitioner

Who: Working compliance professionals who need depth in their domain and breadth across adjacent areas. Route: - Start: Chapters 1, 2, 3 (context and ecosystem) - Core: Your domain chapters from Parts 2, 3, or 4 - Technology grounding: Chapter 4, then relevant chapters from Part 5 - Strategy: Part 7 (Chapters 35–39) - Ethics and governance: Selected chapters from Part 6

Path 3: The Technology Professional

Who: Data scientists, engineers, and product managers supporting compliance functions. Route: - Start: Chapters 1, 4, 5 (domain context and data) - Technology depth: Part 5 (Chapters 23–28) - Domain specifics: Part 2 (AML/KYC) and/or Part 4 (trading) depending on your team - Governance: Chapter 26 (XAI), Chapter 29 (bias), Chapter 30 (AI Act)

Path 4: The Executive Reader

Who: C-suite, board members, and senior leaders who need strategic literacy without operational depth. Route: Chapters 1, 3, 35, 38, 39, and the Part 8 capstone. Skim section headings throughout to build vocabulary.

Path 5: The Global RegTech Professional

Who: Professionals operating across multiple jurisdictions. Route: Sequential reading recommended, with extra attention to Chapter 2, Chapter 17, Chapter 32, and the regulatory alert callouts throughout.

Working with the Code

Python code appears in three forms in this book:

1. Inline snippets — Short excerpts illustrating a specific concept, embedded in the chapter text.
2. Full examples — Complete, runnable scripts in code/example-XX-{name}.py within each chapter folder.
3. Case study code — Longer implementations tied to the chapter case studies, in code/case-study-code.py.

Setup: Install dependencies with pip install -r requirements.txt from the repository root.

Pedagogy: Code in this book is written for clarity, not production performance. Variable names are long and descriptive. Comments explain the "why," not just the "what." When you see production shortcuts in real systems, you will know what they are abbreviating.

If you are not a programmer: Read the code blocks as you would a recipe — you do not need to cook it yourself to understand what it produces. The surrounding text always explains what the code does and why.

Using the Chapter Components

Each chapter contains seven components. Here is how to use them:

index.md — Main Chapter Content The core 8,000–12,000 words. Read it once for comprehension, then return to specific sections as reference.

exercises.md — Practice Problems A mix of conceptual questions, applied scenarios, and (where relevant) coding challenges. Even if you don't write out answers, reading the questions after finishing the chapter is valuable for identifying gaps.

quiz.md — Self-Assessment 20–25 questions (multiple choice, short answer, scenario-based). Use these to verify retention, not just comprehension.

case-study-01.md and case-study-02.md Extended scenarios, typically 1,500–2,500 words each. These are where abstract concepts meet messy reality. Case Study 1 is usually tied to the chapter's recurring characters. Case Study 2 often introduces a different institutional context.

key-takeaways.md A 1–2 page synthesis of the chapter's essential points. Use it before re-reading the chapter (to orient) and after (to consolidate).

further-reading.md Annotated bibliography with brief descriptions. Organized by depth: "Essential," "For Practitioners," and "For the Curious."

Navigating the Appendices

A Note on Currency

Regulatory requirements change. The frameworks described in this book reflect their status as of early 2026. Always verify specific requirements against current primary sources before relying on them for compliance decisions. Where a regulatory requirement has changed significantly since this book was written, your jurisdiction's regulatory authority website is the authoritative source.

Getting the Most from the Characters

The recurring characters — Maya, Rafael, Priya, and Cornerstone — are more than narrative decoration. Their situations are designed to illustrate the real trade-offs that compliance professionals face. As you read:

• Ask what you would do in their position before reading how they decide.
• Notice the constraints they operate under: budget, organizational politics, regulatory ambiguity, technology limitations.
• Watch the arcs develop. The decisions they make in early chapters have consequences that surface later.

By Chapter 40, you will know these practitioners well. That familiarity is a pedagogical tool — it makes abstract principles concrete and memorable.