Agentic Model Risk Management: Industrializing Risk Ranking, Validation, and Monitoring

Agentic Model Risk Management: Industrializing Risk Ranking, Validation, and Monitoring — Ai4

Ai4

AI-assisted summary of Agentic Model Risk Management: Industrializing Risk Ranking, Validation, and Monitoring — original source. Check the original for full context.

Source published:

Detailed notes

## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=4s) Financial Services Model Risk 101 and the Four Lines of Checking

Coming from a traditional technology background before entering financial services, Freddy Lecue recalls experiencing a bit of a shock at how rigorous, structured, and heavily regulated the modeling lifecycle is in banking. In highly regulated financial institutions, deploying an AI or mathematical model into production requires extreme caution. The lifecycle is not handled solely by the model developers; instead, it is governed by a strict multi-layered defense and oversight architecture designed to catch potential failures before they hit production.

The governance structure is split across four distinct layers of checking:

``` +---------------------------------------------------------------+ | Line 4: Regulators | | (External oversight checking entire institution) | +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Line 3: Audit | | (Validates that the 2nd line performed correctly) | +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Line 2: Model Risk Management | | (Challenges models, builds alternative solutions, edge cases)| +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Line 1: Front Line | | (Model developers building, testing, monitoring models) | +---------------------------------------------------------------+ ```

- **First Line (Front Line):** The primary modeling teams who build, train, test, evaluate, and monitor the models. - **Second Line (Model Risk Management):** An independent body that challenges the model, builds alternative challenger models, investigates potential edge cases, and probes what could go wrong. - **Third Line (Audit):** An internal audit body that verifies the second line performed its validation and governance duties thoroughly. - **Fourth Line (Regulators):** External regulatory bodies inspecting the institution to ensure complete compliance across all previous layers.

---

[02:03](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=123s) The Six-Stage Risk Modeling Lifecycle and Frictions

In large financial institutions like Wells Fargo, the model risk management lifecycle spans six core stages from initial concept to ongoing updates. Across these stages, immense friction occurs due to manual handoffs, heavy communication overhead, and subjective human interpretations of policy.

``` +-----------+ +-------------+ +------------+ | 1. Model |-->| 2. Model |-->| 3. Model | | Identify| | Development| | Validation | +-----------+ +-------------+ +------------+ | +-----------+ +-------------+ v | 6. Model |<--| 5. Model |<--+------------+ | Change | | Monitoring | | 4. Model | +-----------+ +-------------+ | Review | +------------+ ```

The six sequential stages are: 1. **Model Identification:** Determining if a proposed algorithm qualifies as a model and assessing its reputation, cost, and monetary risk impact to assign a risk tier. 2. **Model Development:** Front-line teams develop the model, establish documentation, and agree on risk tiers. 3. **Model Validation:** Independent second-line validators take the model, code, and data to stress-test and challenge its performance. 4. **Model Review:** Control and governance teams review validation work against lengthy checklists to ensure regulatory and policy compliance. 5. **Model Monitoring:** Continuous oversight once the model is deployed in production to flag performance anomalies or drift. 6. **Model Change:** Adjusting or retraining models when new features or characteristics become available.

#### Friction Points in the Traditional Lifecycle: - **Manual Handoffs:** Front-line teams hand incomplete documentation or code to second-line validators, forcing slow back-and-forth cycles via emails, Teams calls, and manual meetings. - **Rework Loops & Inconsistent Standards:** Different human validators interpret corporate policies, requirements, and guidelines differently, leading to inconsistent validation rigor and redundant rework. - **Long Cycle Times:** Validation processes drag on over multiple weeks or months. - **Infrequent Monitoring Oversight:** Traditional models are monitored on rigid, sparse schedules (e.g., quarterly, bi-annually, or annually), which is entirely inadequate for rapidly evolving generative AI models.

---

[05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) Transitioning to an Agentic Operational Model

To resolve these operational bottlenecks, Wells Fargo is shifting from manual, fragmented, and periodic workflows to an agentic operational model. Rather than removing humans, the goal is to keep human experts firmly "in the loop" while AI agents handle heavy-lifting tasks, code execution, document generation, and checklist verification.

"Agents are all over... part of the process that you do with human-in-the-loop." The human validator shifts from a manual executor to an authoritative reviewer who signs off on agent-generated outputs, accelerating multi-week processes down to days.

``` +------------------+ +-------------------+ +------------------+ | Step 1: Human | | Step 2: Agent | | Step 3: Human | | Initiation |---->| Execution |---->| Sign-off | | (Devs/Validators | | (Tests, Docs, | | (Stamp & Human | | submit inputs) | | Interpretations) | | Validation) | +------------------+ +-------------------+ +------------------+ ```

#### Five Agentic Workflow Stages: - **Risk Screening & Ranking Agent:** Automatically collects front-line model information, compares it with similar past models, evaluates materiality, and proposes a risk-tier score accompanied by a detailed written justification. - **Development Documentation Generator Agent:** Verifies whether developer documentation meets all second-line evaluation standards before formal validation begins. - **Validation Agent:** Automatically spins up the model in the appropriate infrastructure, runs comprehensive test libraries across historical edge cases, builds challenger solutions, produces performance charts, and identifies risk findings. - **Review Agent:** Automates routine governance checklist reviews (e.g., peer reviews, horizontal reviews, and operational reviews) to reduce massive resource overhead. - **Monitoring Engine:** Shifts model oversight from periodic schedules to near-real-time tracing and anomaly flagging.

---

[13:34](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=814s) Architecture: Meta-Agents, Skills, and MCP Servers

The technical framework underlying Wells Fargo's agentic risk system relies on a modular, multi-layered architecture where meta-agents orchestrate specialized capabilities driven by codifying corporate playbooks into machine-executable "skills."

``` +---------------------------------------------------------------+ | User Personas & Applications (Developer, Validator, Owner) | +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Meta-Agent Orchestrator (Selects and chains specific agents) | +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Specialized Agents & Skills (Markdown Playbooks / Instructions)| +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Model Context Protocol (MCP) Servers (Data, Policy, Databases)| +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Execution & Compute Layer (Cloud / On-Prem Inference & SQL) | +---------------------------------------------------------------+ | +---------------------------------------------------------------+ | Data & Evidence Storage (Audit-ready artifacts & traces) | +---------------------------------------------------------------+ ```

- **Meta-Agent Orchestration:** When a user initiates a task at intake, a central meta-agent dynamically selects, routes, and orchestrates specialized domain agents based on the request. - **Playbooks-as-Skills:** Corporate policy documents and validation manuals are passed through skill creators (leveraging Anthropic and OpenAI formats) to turn static text into executable Markdown skill files. This guarantees agents interpret validation rules identically every time. - **Model Context Protocol (MCP) Integration:** Agents connect to enterprise data, code bases, models, and policy databases via dedicated MCP servers. - **Execution & Evidence Layer:** Agents execute SQL queries, run model inferences, and run code evaluations in isolated cloud or on-premises compute environments, persisting all qualitative and quantitative results into audit-ready evidence storage.

---

[17:43](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1063s) Stage-by-Stage Agent Execution in Practice

The implementation of specific domain agents highlights how human sign-off steps are embedded throughout the model risk management flow:

- **Risk Ranking Agent Workflow:** Model developers submit model specifications into the system. The agent executes against risk-ranking skill playbooks, calculates a risk-tier rating with supporting rationale, and routes it to validators who accept or amend the rating before final sign-off. - **Validation Agent Workflow:** Validators feed the model object and data into the system. Orchestrated checker and tester agents execute automated test routines, construct validation documentation, plot visual diagnostics, and summarize potential risk findings for validator sign-off. - **Continuous Monitoring Engine:** Real-time traces and execution outputs are streamed into a risk oversight engine that automatically flags anomalies or performance degradation, moving the team away from traditional periodic reviews.

## Video description Freddy Lecue - Head of Frontier AI Models, Wells Fargo

Model risk management today remains highly manual, sequential, and fragmented across development, validation, and monitoring, leading to slow cycle times, inconsistent outputs, and scaling bottlenecks. We are building and operationalizing a suite of AI agents that execute end to end model risk workflows - including risk ranking, documentation generation, validation, and continuous monitoring - while keeping humans firmly in control. These agents codify domain expertise into reusable capabilities, standardize validation practices, and enable scalable, audit ready outputs across the model lifecycle. Early results show significant acceleration in validation timelines (e.g., multi week processes reduced to days or weeks), alongside meaningful efficiency gains across model risk teams.

[Source](https://www.youtube.com/watch?v=4GWf1YLd9lk)

中文简报

智能体模型风险管理:推进风险定级、验证与监控工业化 富国银行传统模型风险管理因大量手动交接导致验证周期冗长,耗时可达数月。为此,团队正推进端到端 Agentic 运营模式转型,依托 Meta-Agent 编排架构与 MCP 协议固化合规标准,在人机协同下由 AI Agent 承接风险排级、自动化测试与近实时连续监控,将处理耗时大幅缩短至数天,让人类专家得以专注于最终审核签署。 富国银行(Wells Fargo)的模型风险管理受制于四道防线监管体系,传统六阶段生命周期因大量手动交接与政策主观解读,导致验证流程长达数周至数月。 (2:03) 团队正推进端到端 Agentic 运营模式转型,在保持人机协同(Human-in-the-loop)的前提下,由 AI Agent 承接风险定级、文档生成与模型验证,将耗时压缩至数天。 (5:53) 系统依托 Meta-Agent 编排架构与 MCP 协议连接企业数据,将合规手册固化为可执行的 Markdown Skill,确保验证标准统一且全程留存审计证据。 (13:34) 具体落地覆盖风险排级、自动化测试验证及近实时连续监控引擎,让人类专家从繁重执行中抽离,专注于最终把关签署。 (17:43)

Reading summary

To overcome operational bottlenecks and subjective manual reviews in heavily regulated banking environments, Wells Fargo is transitioning its model risk management to an agentic architecture that keeps human experts in the loop. Presenting for Ai4, Freddy Lecue details how specialized AI agents industrialize risk screening, validation testing, and real-time monitoring while preserving strict regulatory compliance. Multi-Layer Governance and Traditional Lifecycle Bottlenecks (0:04) In banking, deploying models requires navigating four defensive tiers: first-line developers, second-line Model Risk Management (MRM) validators, third-line internal audit, and fourth-line external regulators. The traditional six-stage lifecycle—spanning model identification, development, validation, review, monitoring, and change—suffers from significant operational friction. Incomplete handoffs between development and validation teams trigger repetitive communication cycles across emails and meetings. According to Lecue, subjective human interpretations of corporate policies cause inconsistent validation rigor and redundant rework, extending validation cycles over weeks or months. Furthermore, legacy monitoring relies on sparse periodic intervals, such as quarterly or annual reviews, which Lecue identifies as inadequate for tracking rapidly evolving generative AI systems. The Human-in-the-Loop Agentic Workflow (5:53) Wells Fargo's agentic model shifts human practitioners from manual executors to authoritative reviewers without eliminating oversight. The workflow follows a three-step structure: human initiation, automated agent execution, and human validation sign-off. Lecue notes that automating documentation generation, code execution, and checklist verification accelerates multi-week tasks down to days. The framework introduces five specialized stages: a Risk Screening and Ranking Agent that assesses materiality against historical models; a Documentation Generator Agent that checks developer submissions against second-line standards; a Validation Agent that stress-tests edge cases and generates challenger models; a Review Agent that automates compliance checklists; and a continuous Monitoring Engine. Modular Architecture via Meta-Agents and MCP (13:34) The technical framework relies on a multi-tiered architecture orchestrated by a central meta-agent. Upon receiving user requests, the meta-agent dynamically selects and chains specialized agents. To eliminate subjective rule interpretation, corporate policies and validation manuals are converted into machine-executable Markdown skill files using Anthropic and OpenAI formats, ensuring consistent evaluation across all models. Connectivity across enterprise databases, code repositories, and policy manuals is handled through Model Context Protocol (MCP) servers. The execution layer runs code evaluations, SQL queries, and model inferences within isolated cloud or on-premises environments, persisting all quantitative metrics and qualitative findings into audit-ready evidence storage. Automated Execution from Intake to Real-Time Monitoring (17:43) In practice, domain agents execute specific validation and governance tasks under continuous human oversight. For risk ranking, developers submit model specifications, prompting the agent to apply risk playbooks, calculate risk-tier ratings, and provide written rationale for second-line validator approval or amendment. During validation, automated checker and tester agents evaluate model objects and datasets, construct challenger solutions, run historical edge cases, and produce diagnostic plots alongside summarized risk findings. In production, the monitoring engine ingests real-time traces and execution outputs, automatically flagging performance drift and anomalies to replace legacy calendar-based reviews. By codifying policies into executable skills and deploying meta-agent orchestration, Wells Fargo aims to standardize risk governance across all four lines of defense. The transition shifts model risk management from manual, periodic checkpoints to continuous, audit-ready operational oversight without removing human sign-off.

精炼阅读摘要

富国银行(Wells Fargo)在应对传统金融模型风险管理中繁杂的人工交接、主观标准差异与漫长周期的痛点时,正逐步构建以“人类在环”(Human-in-the-loop)为核心的智能体化(Agentic)运营架构。该架构通过元智能体(Meta-Agent)编排与可执行的技能手册,在确保合规与人工最终签字的前提下,将原本长达数周乃至数月的模型定级、独立验证与合规审查周期压缩至数天,并推动风控由定期抽查转向准实时监控。 四道防线约束与传统六阶段治理瓶颈 (0:04) 在受到严格监管的金融服务行业中,AI及数学模型的投产必须遵循极其审慎的防御与监督架构。据技术专家 Freddy Lecue 介绍,银行业的模型治理横跨四道防线:第一道防线为构建、测试与监控模型的一线研发团队;第二道防线为独立挑战模型、构建挑战者模型并测试极端边界情况的模型风险管理机构(MRM);第三道防线为核查二线履职完备性的内部审计;第四道防线则是执行全面外部监管的监管机构。这一链条确保了模型在上线前能被充分排查潜在故障。 然而,涵盖模型识别、模型开发、模型验证、模型审查、模型监控与模型变更六大阶段的传统生命周期存在严重的运营摩擦。一线与二线之间往往依赖电子邮件、Teams 通话与线下会议进行低效的人工交接;不同的人类验证人员对公司政策与指南的主观解读各异,导致验证标准参差不齐并引发大量返工;验证周期通常拖延数周至数月;更为关键的是,传统季度、半年度或年度的低频监控节奏,已完全无法适应变化迅速的生成式 AI 模型的管理需求。 “人类在环”的五类智能体工作流重塑 (5:53) 为消除上述运营瓶颈,富国银行转向了由智能体驱动的运营模式。这一转型的核心并非剔除人类,而是坚持“人类在环”,使人类验证专家从繁重的底层手动执行者转变为最终审核与签署的权威决策者。通过将代码执行、文档编写与合规检查清单交给智能体处理,原本数周的流程被缩短至数天,形成了“人类发起、智能体执行测试与文档、人类最终签字确认”的标准闭环。 该体系覆盖了五大关键智能体角色:风险筛选与定级智能体负责归集一线信息、对标历史类似模型、评估重要性并自动给出附带详尽理由的风险等级评分建议;开发文档生成智能体在一线移交二线前预先检验文档规范;验证智能体自动搭建运行环境、调度历史极端案例测试库、构建挑战者模型、绘制性能图表并整理风险发现;审查智能体自动化执行针对同行评审和运营评审的常规合规清单;监控引擎则将低频的周期性审查转变为针对生产异常的准实时追踪。 技术框架:元智能体、手册技能化与MCP协议 (13:34) 富国银行智能体风控系统的底层技术由模块化、分层的架构支撑。系统面向开发者、验证者与所有者等不同角色,在任务入口设置了中心元智能体(Meta-Agent)协调器。当用户发起任务请求时,元智能体会动态选择、路由并编排执行特定任务的专业领域智能体。 为了消除人为解读政策带来的标准不一,该系统推行“手册即技能”(Playbooks-as-Skills)的机制。企业内部的政策制度与验证操作手册通过技能生成工具(采用 Anthropic 和 OpenAI 格式),从静态文本转化为机器可执行的 Markdown 技能文件,确保智能体在每次执行验证规则时保持严格的一致性。底层则借助模型上下文协议(Model Context Protocol, MCP)服务器,将智能体与企业数据源、代码库、模型资产和政策数据库安全相连;最终在隔离的云端或本地算力环境中执行 SQL 查询、推理与代码测试,并将所有定性与定量分析沉淀为符合审计要求的证据留痕资产。 落地实测:风险定级、挑战测试与持续监控 (17:43) 在实际业务落地中,具体领域智能体的执行全流程均嵌入了人类把关节点。在风险定级流程中,模型开发者提交模型规格后,定级智能体依据风险分级技能手册运行,计算出风险层级并出具支撑依据,随后直接推送给二线验证人员,由后者进行核准或修订后正式生效。 在模型验证环节,验证人员将模型对象与数据集输入系统,由受编排的检查与测试智能体自动执行成套测试套件、生成验证报告初稿、绘制诊断图表并总结潜在风险发现,最终呈递给人类验证人员签字封存。而在模型投产后,持续监控引擎接收并分析准实时的数据流与执行痕迹,一旦出现性能衰减或数据漂移便自动告警,彻底摆脱了过去僵化的周期性审查模式。 富国银行的模型风控智能体化实践表明,将企业政策转化为机器可执行的代码规范,能显著压缩模型上线与验证周期,同时保留严格的人类问责制与审计证据链。然而,面对生成式 AI 等新型算法的快速更迭,如何在高度监管的高压环境下,长期平衡自动化测试的覆盖深度与人类专家对边缘风险的定性裁量权,仍是该体系持续演进中需要应对的现实考题。

Detailed notes — zh

## Background 本内容由频道 Ai4 于 2026 年 8 月 17 日发布在 YouTube 平台上,主讲人为富国银行(Wells Fargo)前沿 AI 模型负责人 Freddy Lecue。视频简介指出,当前模型风险管理存在高度人工化、串行割裂与效率低下等瓶颈,富国银行正构建端到端的 AI Agent 套件以实现风险评级、文档生成、验证与监控的工业化,在保持人类把关的前提下大幅缩短验证周期并提升质检效率。 ## TL;DR 演讲系统拆解了在严苛金融监管下,如何利用 AI Agent 重塑传统的模型风险管理(MRM)全生命周期。传统人工模式长期受困于文档交接摩擦、不同验证员主观偏差及低频滞后的监控机制;富国银行通过“人在回路”(Human-in-the-Loop)架构,将操作手册转化为标准化技能(Skills),并结合 MCP 协议构建了覆盖分级、验证、评审与实时监控的专用智能体池。该体系不仅使整个风控生命周期耗时平均缩短 50%,更实现了从“抽样审查”向“全量自动化覆盖”与原生“审计就绪”(Audit-ready)的范式跃迁。 ## Atmosphere & style 整场演讲呈现出一种严谨务实、兼具前沿技术视野与金融合规敬畏感的专业基调。演讲者以自身从科技行业跨界至强监管金融业的“震撼体验”切入,语言条理清晰、直击痛点,既不盲目鼓吹全面替代人类,也毫无冗余的务虚修辞。在层层拆解系统分层架构与工业化落地的过程中,观众能清晰感受到一种冷静而坚定的工程推进感——在极致追求效率提速的同时,始终将控制力、问责制与合规可追溯性置于首位。 ## Key takeaways - [00:04](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=4s) 金融机构受严苛监管制约,建立了由业务建模(第一道防线)、模型风险管理 MRM(第二道防线)、内部审计(第三道防线)及外部监管构成的四重制衡体系。 - [00:04](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=4s) 第二道防线(MRM)贯穿模型全生命周期,涵盖模型识别、开发协作、独立验证、治理评审、投产监控与模型变更六大关键环节。 - [02:03](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=123s) 传统人工 MRM 流程充斥着部门间繁重的人工交接摩擦、不同验证人员主观差异导致的反复返工,以及季度/年度低频审查造成的监控严重滞后。 - [05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) Agentic 运营模式的核心并非取代人类,而是构建深度协同的“人在回路”(Human-in-the-Loop)架构,AI 负责机械性测试与初稿生成,人类专家牢牢把控最终签署决策权(Sign-off)。 - [05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) 团队在风险识别、文档生成、独立验证、横向评审与实时监控等关键阶段分别部署了专用 AI Agent,实现端到端的风险工作流承接。 - [11:46](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=706s) 系统严格遵循三步闭环运行逻辑:人类发起提交、Agent 解析指令运行测试并生成风险发现、人类专家复核证据链并盖章签署以确保合规。 - [11:46](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=706s) 架构层借助 Skill Creator 工具将业务合规手册(Playbook)编译为结构化 Markdown 技能文件,将专家领域经验精确编码为 Agent 可执行的标准技能。 - [11:46](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=706s) 采用模型上下文协议(MCP)搭建中间连接层,安全打通企业异构模型库、基准数据集与合规政策库,并自动沉淀执行证据以备审计。 - [17:55](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1075s) 持续风险监督引擎打破传统低频抽检模式,通过持续捕获线上推理轨迹并执行评估,实现模型风险异常与漂移指标的分钟级预警响应。 - [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) 在智能体赋能下,MRM 全生命周期各环节平均耗时缩短 50%,同时消除了验证人员之间的主观判断偏差,实现输出结果的高度标准化。 - [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) 风控质检范式发生根本性跃迁:从以往受人力与算力制约的“人工抽样检查”,升级为对全量模型的 100% 自动化全覆盖验证与扫描。 - [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) Agent 执行全流程中生成的各类工件均被自动保存归档,构建出端到端的数据血缘与追踪路径,使交付成果原生具备“审计就绪”(Audit-ready)特性。 - [20:47](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1247s) 变革践行“更快并不意味着放松监管”(Faster doesn't mean less control)的理念,通过专家经验技能化与明确的人类问责制,达成运行效率与风险合规的双赢。 ## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=4s) 金融强监管背景下的“四道防线”与模型风险管理生命周期 富国银行(Wells Fargo)前沿 AI 模型团队负责人 Freddy Lecue 介绍了团队在构建基础模型之外的另一项核心探索:如何运用 AI 全面加速并重构传统的模型风险管理(Model Risk Management, MRM)流程。对于非金融领域的从业者而言,金融业的模型治理机制往往带来巨大的文化冲击。Freddy Lecue 直言,自己此前来自科技行业,当跨界进入金融机构时,金融体系内严苛的模型全生命周期管理方式让他感到了“不小的震撼”("a bit of a shock")。在高度受监管的金融机构中,任何模型投产都必须如履薄冰,背后建立了一套层次分明的多重制衡体系: ```mermaid flowchart TD accTitle: 金融机构模型风险管控与四道防线示意图 accDescription: 展示从一线建模到外部监管的四层监督流程与MRM核心环节 subgraph DefenseLines ["金融机构四道防线管控体系"] L1["第一道防线:业务与建模团队\n(Front Line: 建模、开发、基础测试)"] L2["第二道防线:模型风险管理团队\n(Second Line: MRM 独立验证、挑战者方案)"] L3["第三道防线:内部审计部门\n(Third Line: Audit 流程审计与合规检查)"] L4["第四道防线:外部金融监管机构\n(Regulators: 顶层合规核查)"] L1 -->|提交模型与文档| L2 L2 -->|验证通过与留痕| L3 L3 -->|合规报告| L4 end ``` - **第一道防线(Front Line / First Line)**:业务建模团队,负责模型的构思、特征工程、代码开发、基础测试评估以及日常监控。 - **第二道防线(Second Line)**:独立的模型风险管理(MRM)团队,负责对第一道防线的模型发起“挑战”。他们会构建挑战者解决方案(Challenger solutions),挖掘被遗漏的极端案例(Edge cases),排查潜在失效场景。 - **第三道防线(Third Line)**:内部审计团队(Audit),负责严格审查第二道防线的验证工作是否扎实合规。 - **监管机构(Regulators)**:处于顶层的外部监督者,随时调阅全流程记录以确保万无一失。 在第二道防线的 MRM 职责下,完整的模型生命周期通常包含六个环节:模型识别(Identification,评估声誉、成本与资金影响并确定风险分级)、开发协作(Development,对齐文档标准)、模型验证(Validation,独立测试与挑战者评估)、治理评审(Review,基于清单进行把关控制)、投产监控(Monitoring,捕获异常表现),以及后续根据新特征进行模型变更(Changes)。 ### [02:03](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=123s) 传统模型风险管理的六大环节与现实摩擦痛点 传统的人工模型风险管理流程在各大金融机构普遍存在,但跨部门协同中充斥着繁重的人工摩擦与效率瓶颈。Freddy Lecue 聚焦于识别、开发、验证、评审和监控这五大核心环节,剖析了传统模式下的三大核心痛点: ```mermaid flowchart LR accTitle: 传统模型风险管理生命周期的核心阶段与痛点 accDescription: 展示识别、开发、验证、评审、监控五大阶段及主要摩擦点 A["1. 模型识别\n(Identification)"] --> B["2. 模型开发\n(Development)"] B --> C["3. 独立验证\n(Validation)"] C --> D["4. 治理评审\n(Review)"] D --> E["5. 持续监控\n(Monitoring)"] subgraph PainPoints ["传统流程核心痛点"] F["人工交接摩擦\n(文档缺失与反复沟通)"] G["返工循环与标准不一\n(不同验证员主观偏差)"] H["周期漫长与监控滞后\n(季度/年度低频回溯)"] end ``` 第一道防线在完成模型开发后将文档交接给第二道防线时,验证人员往往会发现关键要素缺失、代码无法复现,随后陷入无休止的邮件沟通、Teams 会议和返工循环。不仅如此,尽管机构内部制定了完备的政策(Policies)、要求与检查清单(Checklists),不同验证人员之间依然存在主观理解差异;“验证员 A 和验证员 B 可能会采用截然不同的解决思路”,导致审查标准与文档质量参差不齐。 更为严峻的是漫长的周期与低频滞后的监控体系。传统模型的监控频率通常取决于风险等级,多为按季度、半年度甚至年度进行回溯。然而,随着生成式 AI(GenAI)和大模型的大规模涌入,每年一次的周期性审查完全无法应对实时波动的风险,必须转变为更高密度的敏捷管控机制。 - **人工交接摩擦(Manual handoffs)**:第一道防线文档不全导致第二道防线无法直接复现,带来跨团队间反复拉扯。 - **返工与主观偏差(Rework loops & inconsistent interpretation)**:人类对合规手册(Playbook)的理解存在偏差,造成输出格式与严格程度不一。 - **监控周期滞后(Long cycle times & limited oversight)**:传统低频回顾无法应对生成式 AI 时代的动态风险暴露。 ### [05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) 从串行人工到 Agentic 运营模式:Human-in-the-Loop 范式 为打破“高度串行、人工割裂、依赖领域经验且周期漫长”的旧模式,团队开始将整个风险管理工作流向 Agentic(智能体化)运营模式迁移。这一变革并非要取代人类验证员,而是构建深度协同的“人在回路”(Human-in-the-Loop)架构:AI Agent 负责执行复杂的机械性任务、跑测试代码与生成初稿,人类专家则牢牢掌握最终决策与签署权(Sign-off)。 在这一模式下,各大环节均有专门的 AI Agent 承接任务: 1. **风险分级 Agent(AI Risk Rank Agent)**:在识别阶段吸收第一道防线提交的模型信息与历史相似案例,严格对照治理政策与操作手册(Playbook),自动化生成风险层级建议及量化依据。 2. **文档生成 Agent(Model Dev Documentation Generator)**:协助开发团队规范化生成第二道防线所需的完备材料,并在交接前自动预检是否满足验证标准。 3. **验证 Agent(AI Validation Agent)**:承担工作量最繁重的环节。过去验证人员需要耗费数周在不同计算环境中搭建环境、复现模型、挑选挑战者算法,而验证 Agent 能够直接调用标准测试库,自动化执行代码评估、挖掘分布外数据(OOD, Out-of-Distribution)风险并生成直观图表与“风险发现”(Risk findings)报告。 4. **评审 Agent(AI Review Agent)**:金融行业内部存在大量的同行评审(Peer review)、横向评审(Horizontal review)与运营评审。这部分工作以往常沦为耗费大量人力的“勾选框形式主义”("checkbox exercise"),Agent 的介入极大压缩了治理与合规核查的综合成本。 5. **监控 Agent(Continuous Monitoring)**:将静态的季度抽检转变为近乎实时的持续风险监测。 ### [11:46](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=706s) Agent 系统三步闭环与分层架构设计(Playbook、Skill 与 MCP) Freddy Lecue 详细拆解了 Agent 系统的“三步闭环”运行逻辑以及底层的工程架构分层。整个交互流程严格遵循三步范式: ```mermaid flowchart LR accTitle: Agent 模型风险管理的三步闭环流程 accDescription: 包含第一步人类发起、第二步智能体执行与第三步人类审核审批 Step1["第一步:人类发起\n(开发者/验证员提交模型与文档)"] --> Step2["第二步:Agent 执行\n(解析Playbook/运行代码/生成Findings)"] --> Step3["第三步:人类审批\n(专家复核证据图表并盖章 Sign-off)"] ``` - **第一步(人类发起任务)**:模型开发者或风险验证员提交模型文件、指标参数或待审文档。 - **第二步(Agent 自动化执行)**:Agent 接收输入,执行质量检测、运行针对性测试代码、解释实验数据,并输出包含图表、表格与定性/定量风险发现的结构化文档。 - **第三步(人类专家终审)**:人类验证员复核由 Agent 整理好的完整证据链,进行确认或人工微调,最后正式盖章签署(Sign-off),确保全流程符合内部审计规范(Audit-ready)。 ```mermaid flowchart TD accTitle: 模型风险管理 AI Agent 平台分层技术架构 accDescription: 展示用户角色层、应用层、Agent编排层、MCP数据接口层与计算执行层 subgraph TopLayer ["交互与角色层"] Users["用户角色\n(模型开发者 / 验证员 / 业务负责人)"] Apps["应用终端\n(治理平台 Governance / 编程助手 Coding Assistant)"] Users --> Apps end subgraph AgentLayer ["智能体与技能编排层"] MetaAgent["元编排 Agent\n(Meta Agent / Orchestration)"] Skills["Markdown Playbook 技能库\n(Skill Creator 生成的专属指令集)"] AgentPool["专用智能体池\n(分级 Agent / 验证 Agent / 评审 Agent 等)"] Apps --> MetaAgent MetaAgent --> Skills Skills --> AgentPool end subgraph InfraLayer ["数据与执行底层"] MCP["MCP 服务层 (Model Context Protocol)\n(对接模型库、数据库、合规政策库)"] Compute["执行与存储层\n(本地/云端计算推理、SQL执行、证据存储)"] AgentPool --> MCP MCP --> Compute end ``` 在系统底层架构上,系统自上而下被解构为清晰的模块层次: - **技能实例化机制(Skill Creator & Markdown Playbook)**:业务人员日常遵循的复杂合规手册与操作指南(Playbook)被转化为结构化的 Markdown 技能文件。通过借助行业主流的技能生成工具(Skill Creator),合规指南被直接“编译”为 Agent 可精准理解并无歧义执行的特定技能(Skills),从而使通用大模型精准特化(Personalized)为具备特定领域经验的专业 Agent。 - **上下文连接层(MCP Servers)**:借助模型上下文协议(Model Context Protocol, MCP)搭建数据服务桥梁,打通企业内部异构的基础设施,使 Agent 能够安全访问模型对象、基准数据集以及最新的监管政策数据库。 - **计算执行与证据存储(Execution & Storage)**:Agent 在本地或云端算力环境中执行代码、下发 SQL 查询、运行模型推理压测,并将产出的图表、量化指标和结构化报告持久化沉淀至底层证据库(Data Storage),随时供审计团队追溯。 ### [17:55](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1075s) 各阶段 Agent 的具体落地工作流 Freddy Lecue 快速梳理了几个核心专用 Agent 在实际工作流中的执行细节: - **风险分级 Agent(AI Risk Rank Agent)**:开发者上传新模型的基础特性与元数据信息;Agent 调用内置风险分级政策的 Playbook 技能,结合模型业务重要性与资金影响进行推理,自动输出建议的风险评级(Risk Rank)与详尽的判定理由(Rationales);随后交由人工验证员确认、调整或直接批准。 - **验证 Agent(AI Validation Agent)**:验证员输入待测模型与基准要求后,元 Agent 编排调度具备检查(Checker)与测试(Tester)技能的子 Agent 协作运行,自动生成包含挑战者测试对比、分布外数据鲁棒性分析的完整模型验证报告初稿。 - **评审 Agent(AI Review Agent)**:在验证文档完成后,评审 Agent 自动化对照各项治理指标和横向比对清单进行合规扫描,确保同类业务线的模型受到一致且公允的审查,验证员仅需对照扫描结果进行复核。 - **风险监督引擎(Continuous Risk Oversight Engine)**:在监控环节,该引擎持续捕获模型在线上运行的推理轨迹(Traces)并执行评估,一旦发现异常漂移或违规指标即刻打上风险标记(Flag),真正实现风险隐患的分钟级响应。 ### [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) 智能体赋能下的核心成效:周期减半、全量检测与全链路审计追踪 智能体驱动的模型风险管理(MRM)为整个生命周期带来了颠覆性的效率提升与质量变革。在实施智能体架构后,团队在模型风险分级(Risk Ranking)、模型开发、验证、审核以及监控等各个环节中,平均缩短了 50% 的处理时间。监控机制也彻底从以往低频、滞后的“定期审查”演进为“实时流式监测”。更关键的是,智能体消除了过去由不同验证人员("family of validators")因个人主观习惯或能力差异而产生的标准不一致问题,确保了所有输出结果的高度标准化与严谨性。 此外,智能体在自动化执行过程中生成的全套工件(Artifacts)都会被完整沉淀,自动构建出具备“审计就绪”(Audit-ready)特性的全流程数据血缘与记录追踪。这种极致的扩展能力重塑了风控团队的工作范式:以往由于人力与算力限制,风控与合规团队只能对模型进行抽样检查(Sampling);而在智能体的强力支撑下,团队已经彻底摆脱了抽样限制,能够对全量模型执行全面、无死角的自动化验证与风险合规检查。 ```mermaid flowchart TD accTitle: 传统模型风险管理与智能体驱动模式对比 subgraph Traditional["传统人工/抽样模式"] T1["人工抽样检查<br/>(Coverage 限制)"] T2["周期性滞后审查<br/>(Periodic Monitoring)"] T3["验证标准受人员影响<br/>(结果差异大)"] end subgraph Agentic["智能体驱动工业化模式"] A1["全量自动化检测<br/>(100% Full Execution)"] A2["全天候实时监控<br/>(Real-time Monitoring)"] A3["标准化输出与审计血缘<br/>(Audit-ready Lineage)"] end Traditional -.->|"转型升级:耗时缩减 50%"| Agentic ``` - **全流程提速 50%**:覆盖风险定级、模型开发、独立验证、报告评审及监控全周期。 - **质检范式跃迁**:从传统的“抽样检查”升级为全量模型的自动化全覆盖验证。 - **原生审计就绪**:执行过程中自动保存并归档所有中间工件,提供完整的溯源路径。 --- ### [20:47](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1247s) 核心架构支柱与结语:将专家经验转化为技能,实现速度与控制的双赢 在总结演讲时,演讲者提炼了构建智能体模型风险管理体系的四大基石。其核心在于“可重复执行性”(Repeatable Executions)——借助前沿模型实验室(Frontier Model Labs)提供的 Skill Creator 等工具,风控团队将深厚的领域专业知识(Domain Expertise)精确编码并固化为可复用的“技能”(Skills)。智能体在这些标准化技能之上进行调度与执行,既保证了操作的精确度,又兼顾了灵活性。 然而,自动化并不代表脱离监管。整个系统架构严格确立了“人类问责制”(Human Accountability)与“持续监督”(Continuous Oversight),确保每一步智能体决策背后都有明确的人类责任归属与实时把控。正如演讲者最后强调的:"Faster doesn't mean less control."(更快并不意味着放松监管)。智能体化改造的根本目标,是构建一个反应更快、标准更一致且具备完整可追溯性的现代化模型风险管理体系。 - **专家经验技能化(Expertise as Skills)**:利用前沿模型工具将资深专家的风控经验转化为标准化代码与可执行技能。 - **人在回路与持续监督**:智能体执行任务的同时,由人类专家把控最终责任并进行全流程持续监督。 - **速度与合规兼备**:在大幅压缩流程周期的同时,全面强化风控的一致性、合规性与可追溯性。 ## Notable quotes > [00:04](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=4s) a bit of a shock — Freddy Lecue > [02:03](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=123s) 验证员 A 和验证员 B 可能会采用截然不同的解决思路 — Freddy Lecue > [02:03](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=123s) 每年一次的周期性审查完全无法应对实时波动的风险,必须转变为更高密度的敏捷管控机制。 — Freddy Lecue > [05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) 这一变革并非要取代人类验证员,而是构建深度协同的“人在回路”(Human-in-the-Loop)架构:AI Agent 负责执行复杂的机械性任务、跑测试代码与生成初稿,人类专家则牢牢掌握最终决策与签署权(Sign-off)。 — Freddy Lecue > [05:53](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=353s) checkbox exercise — Freddy Lecue > [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) family of validators — Freddy Lecue > [19:45](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1185s) 彻底摆脱了抽样限制,能够对全量模型执行全面、无死角的自动化验证与风险合规检查。 — Freddy Lecue > [20:47](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1247s) Faster doesn't mean less control. — Freddy Lecue > [20:47](https://www.youtube.com/watch?v=4GWf1YLd9lk&t=1247s) 智能体化改造的根本目标,是构建一个反应更快、标准更一致且具备完整可追溯性的现代化模型风险管理体系。 — Freddy Lecue ## Mentioned Freddy Lecue, 富国银行 (Wells Fargo), Ai4, 模型风险管理 (MRM), 模型上下文协议 (Model Context Protocol / MCP), Skill Creator, Frontier Model Labs, 人在回路 (Human-in-the-Loop) ## Video description Freddy Lecue - Head of Frontier AI Models, Wells Fargo Model risk management today remains highly manual, sequential, and fragmented across development, validation, and monitoring, leading to slow cycle times, inconsistent outputs, and scaling bottlenecks. We are building and operationalizing a suite of AI agents that execute end to end model risk workflows - including risk ranking, documentation generation, validation, and continuous monitoring - while keeping humans firmly in control. These agents codify domain expertise into reusable capabilities, standardize validation practices, and enable scalable, audit ready outputs across the model lifecycle. Early results show significant acceleration in validation timelines (e.g., multi week processes reduced to days or weeks), alongside meaningful efficiency gains across model risk teams. [Source](https://www.youtube.com/watch?v=4GWf1YLd9lk)

Source quotes

[0:04] Freddy Lecue: a bit of a shock [2:03] Freddy Lecue: 验证员 A 和验证员 B 可能会采用截然不同的解决思路 [2:03] Freddy Lecue: 每年一次的周期性审查完全无法应对实时波动的风险,必须转变为更高密度的敏捷管控机制。 [5:53] Freddy Lecue: 这一变革并非要取代人类验证员,而是构建深度协同的“人在回路”(Human-in-the-Loop)架构:AI Agent 负责执行复杂的机械性任务、跑测试代码与生成初稿,人类专家则牢牢掌握最终决策与签署权(Sign-off)。 [5:53] Freddy Lecue: checkbox exercise [19:45] Freddy Lecue: family of validators [19:45] Freddy Lecue: 彻底摆脱了抽样限制,能够对全量模型执行全面、无死角的自动化验证与风险合规检查。 [20:47] Freddy Lecue: Faster doesn't mean less control. [20:47] Freddy Lecue: 智能体化改造的根本目标,是构建一个反应更快、标准更一致且具备完整可追溯性的现代化模型风险管理体系。

Original transcript

[0:04] So I'm leading the frontier modeling team in  Fargo. So um and I'm going to give you an overview [0:11] of where we not only on how we build foundation  models. So my team is building foundational models [0:16] but that particular work I'm going  to share with you is how we apply AI [0:21] for accelerating uh model waste management  the old process. So before I move to the topic [0:29] I mean if you're not from the financial service  uh industry it's it I need to give you a 101 right [0:35] because I'm coming from tech uh and I joined uh  before I was in other financial organization and [0:41] was a bit of a shock for me the way the modeling  life cycle is done by modeling I mean AI modeling [0:48] but any modeling right so in in financial  organization it's a very highly regulated [0:55] industry Okay. So that means they mean to be  super careful when they put model in production [1:00] and you don't only have a modeling team that do  the modeling and do the testing evaluations and [1:05] I mean the monitoring. So this is a thing this  what we call it the front line. This is the [1:10] this is the this is the first line. But you do  also have in financial organization in highly [1:15] regulated industry you have this second line. And  this second line is basically taking the model and [1:20] they challenge the model. They build challenges  solutions. They look if any edge cases might be [1:27] dropped out. They will investigate what might go  wrong. And then you have the third line which is [1:32] the audit. The audit check that the second line  did a good job. And then on top of it you have [1:37] the regulators that check that everything has been  doing right. So that that's basically four layers [1:42] of check and things getting right and don't go  wrong. Right. So and and model risk management [1:49] is this second line that do the validation and  um what you see here you see you see the life [1:55] cycle of what's happening in in risk modeling  uh from a risk perspective. So you do basically [2:03] six steps. So you do identify the model you try to  see if the model is of risk for the company from a [2:10] reputation from a from a cost um from a monetary  impact. So you check that. So you you utilitate [2:18] and then you have the team that build the model  and then when they say okay that's the highrisisk [2:23] tier model then they build and they develop  and they agree on the wis tier agree on what [2:27] documentation needs to be done and then the model  is done they don it give it to the validators the [2:33] validators they validate and then after the  validation is done they have to check and this [2:38] is where governance is coming in play and control  is coming in play they check everything has been [2:43] done right and this is the reviewing part it  takes a lot of time because you have a team that [2:48] check the validation is done right and they they  have a lots of checklist to to do and to go over. [2:55] Then you have monitoring. Someone they agree they  validate and then they put the model in production [3:00] and if something off then this is where they  capture they monitor model and then you do [3:07] maybe the model developers get new characteristic  they need to adjust it they can make it better and [3:12] they they want to change it and this is this is  when they do the mod changes and this basically [3:17] this life cycle and and this is in Wells Fargo  but this is in all financial organization the [3:22] same thing is happening you identify you develop  you validate you review monitor and you change [3:29] right and in the AI agency AI world there's a lot  of those step that can be helping with the with [3:36] making things this faster more accurate better  and much more consistent and this is exactly [3:43] what we doing in westago so here are the five main  stages I'm not going to go over the the change [3:50] part I mean at least I show you the six steps  but here I'm going only go over the Five steps [3:56] identification development validation review and  monitoring and there's a lot of frictions a lot of [4:02] frictions so you have manual and over so meaning  uh the front line is building a model they don't [4:09] they they pass it to the second line the second  line look at the documentation they cannot make [4:14] they can replicate it they can they can validate  it right away because they are missing elements [4:18] they go back to the front line the front line  they have meetings email exchange teams calls [4:23] I mean you have a lot of frictions and that's  manual end of that's and and and that's something [4:28] that agents can do if that's properly done  because it's it's not super complicated [4:33] and then you have a lot of we work loops and  cost documentation because if you have validator [4:38] A coming or validator B coming they might have  slightly different way of addressing a problem [4:44] even if you have policies and your requirements  you have checklist even if it's documented [4:49] a validators may have a different interpretation  and that's where an agent If you if you tune the [4:55] agent right all of these documentation about what  you should be doing the policy the guidelines the [5:00] requirements if it's all documented we call  this a playbook if you have a playbook I mean [5:06] the playbook is interpreted is interpreted it  always the same way by your agents by humans well [5:13] agents have different interpretation so that's  where you have in custom documentation and agent [5:17] maybe can help and you have long cycle times and  unlimited continuous overight So usually when a [5:25] model is up in production uh depend on the risk  of the models uh they might be monitored every [5:32] quarter by week by by yearly or maybe once in a  year but it's h with with geni models coming our [5:40] way more and more often. It's not something that  you can only monitor once a year. You need to you [5:45] need to keep monitoring keep keep going. So yeah  so uh so there there are basically issues. So, [5:53] so what we what we did today is well what we  did yesterday is yeah model manual model risk [6:00] workflows uh which is very sequential manual  fragmented domain and periodic side and we [6:08] we move it to agentic operational model. I'm  going to give you a sense of what that means on [6:13] how agents not how they build but exactly what  they do but it's basically every steps in this [6:20] process in the overall process is now tracked  by agents doesn't mean people and validators [6:26] are not part of the story anymore they are  definitely here we have human in the loop [6:32] uh check and review and assistance right so  it just the agent is asked to do some task And [6:41] uh out of those tasks you get some outcome which  might be an output of a checklist check or an [6:46] output of an execution code or test code done or  experimentation done. It's done by agents but the [6:52] human or the validators is is signing off right  it it goes much faster because it doesn't need to [6:59] I mean do it from scratch not the agent is here  to help identifying what what is the risk rank of [7:05] that model and how we can build the model they who  can build the model document the model how we do [7:11] the validation the review and the monitoring all  right so so agents all over they're all part of [7:18] the process that you with human uh in the loop. So  um and I give you a sense of for identification. [7:25] So we have this AI whisk screen with AI with crank  agent which I'm going to show you show details but [7:31] it's basically the one that get all information  from the front line to the similar model [7:38] to describe what it is. I mean anything  about uh um materiality, anything about um [7:45] risk level questions is basically captured by the  agents with policy and guidelines and governance [7:51] part of the documentations. It's it's the  playbook of the risk crank agent. It's [7:56] it's mased by the agent and it's uh and the whisk  crank score is given is given with a justification [8:03] and then same for for development. So you do have  uh model development documentation generator. [8:08] So when the model the front line build their  model they have to provide documentation which [8:13] is reviewed by the second line and when this  is done the front line the second line which [8:20] are the validators they check the documentation  and then they they assess and they they evaluate [8:25] but now you have an agent that is checking that  the documentation is ready to be to be evaluated [8:32] and then validation and that's that's the  probably the where the agent is the most useful [8:37] because validator I mean few weeks back they  they were going well they were getting the code [8:46] and the model and the data and they were first  replicating the solutions or the model and usually [8:51] you don't really have the same infrastructure  and it takes time. It's it's not so easy. [8:55] And when you get that done, they build challenger  solutions. And basically, they build it by waiting [9:00] what might be the best challenger solutions.  And they implement it or they just take it [9:04] on the shelf. They execute it and they have a  bunch of test routines that they run against those [9:09] existing model to check if the front line don't  forget about any I don't know edge cases. And uh [9:17] this is kind of the one of the problem we may have  with machine learning models. they might have some [9:22] uh data which is out of distribution and  it's maybe have been forgotten during the [9:27] the evaluation. So and this validation agent is  is taking over all the test that have been done [9:34] in the past and we have libraries for different  test and validation for different type of model [9:40] get captured they get executed and get the model  object in the right uh infrastructure and platform [9:45] and they do uh this uh execution of code and  then they even do the interpretation. So you get [9:52] you get um you get charts and diagram out of those  test execution with uh agent doing the validation [10:00] and uh and finding and doing risk findings. So  in financial industries risk findings especially [10:06] for the sub line is the big thing. So is there any  any any risk associated to the model that we need [10:13] to communicate with the front line. So they they  need to take it seriously and they need to find [10:18] a solution or at least they know there's a risk  associated when they deploy it and those findings [10:24] are uh phoned partially by agents and validated  by human and then of course human can do more they [10:32] can do one search and and apply more test and find  more risk findings but this is what the validation [10:39] is doing and then you have the AI agents that do  review which is If you're part of the if you're [10:46] part of financial industries and you do your  team or if you know teams that do uh governance [10:52] and control this is basically what they put in  place a bunch of things that need to be checked [10:58] and they're basically checklist and in in in in  our industry it's called peer review horizontal uh [11:06] review operational reviews and a bunch of reviews  that needs to be done to make sure the model has [11:12] been treated fairly across the same population,  the same kind of of models. Uh, and it's it's all [11:19] of those reviews that need to be done and it takes  a lot of time and energy takes resources, people, [11:24] and it's many cases is a checkbox exercise, but it  takes a lot of energy and talk lots of time. So, [11:31] so there's a huge opportunity to reduce um  costs in in this review this review section. [11:37] And then you have monitoring when we move from  periodic to nearly real time. All right. So [11:46] yeah, so give you an idea uh yeah so of the  different type of agents we have. So I mean [11:54] basically three steps and the the agent is  in the step in the middle. So the step one is [12:00] either the model developers or the validators  they initiate a task. So the developer [12:06] uh I mean they they submit a model they submit  a documentation they submit metrics could be [12:11] developers or validators and the agents they take  that documentation they take that model object [12:17] and they they check the quality of the document  or they execute the test against the model [12:23] uh and that what the execution of the agent and  it can do the interpretation and they can write [12:28] the documentations if documentation is needed at  that step. And step three is the human is taking [12:34] control because it's taking all the output  of the agents. So usually they are not this [12:39] they save as different artifacts could be charts  and tables and could be wisings. It could be uh [12:46] any sort of content could be numerical or  could be textual qualitative and quantitative. [12:51] But all of those uh they all condensed and  compacted in a documentation. a documentation [12:57] for the developers or documentation for  the validators that could be traced and [13:01] could be used by the audit team to understand  what has been doing in this overall process. [13:07] And uh so that step three is basically a sign up  by the validators other developers and they they [13:14] basically do one basically put a stamp and say  okay that's been human validated. All right. And [13:20] you do Yeah. And and all of those uh five steps  uh you have those three uh those three those three [13:28] uh roles the developer the agents and the  the developer taking control at the end. [13:34] So just to give you an idea u of kind of the  steps. So on the left hand side this is how [13:41] this is working from the bottom to from the top to  the bottom. So the user you start with an intake [13:47] and then he he has a bunch of he has access to  a bunch of agents that we built and designed [13:52] and um and he won't I don't know if you want to do  with crank with cranking of a of a model then the [13:59] there's there's a meta agent that going to do the  orchestrations and take control of which agents [14:04] you need to use orchestrate those agents and  they're going to use some what we call skills and [14:10] skills is no more than if you're a bit technical  ical than the markdown file with basically [14:17] a playbook uh which has been nicely captured in  a markdown file using uh well a skill yeah I mean [14:28] entropic and open AI they have this skill creators  you can create a skill out of some documentation [14:34] that going to be executed by an agent and that  basically uh instantiate your agent and the right [14:41] hand side are the bunch of skills we So if you  have documentation about how you should do a job [14:47] and you you you have this documentation in your  organizations when you are new starter say hey you [14:52] need to be able to validate you need to edit you  need to check this is the documentation so we call [14:57] this it's a playbook it's a bunch of instructions  and you give it to an a a skill creator [15:04] that's going to create that skill and basically  going to be uh instructions but for the agent [15:10] and those agents are going just to be materialized  by the skill they will be always well I call it [15:17] personalized because they've already personalized  with respect to the skills they need to achieve [15:22] and that skill is whatever is the playbook  that you define using the skill creator and um [15:28] and then yet you have the evidence after you do  the execution of the agent on the specific skill [15:34] and again the skill is it's not something you  build it's something you ask an agent creator [15:39] to build a skill creator to And then  you do have the human review under it. [15:46] So it's very small of things but it  just to give you an idea of kind of the [15:51] the different layers. So you have the personas  on the top you have the different application. [15:57] Uh so depending who is using if it's a model  developers validators or owner they interact with [16:02] different platforms. Uh it could be a governance  platform it could be a coding assistant platform. [16:08] um and but that's where the interactive and then  you have this agent that we build. So those five [16:15] agent that I've shown with crank agents developer  agents they are here and uh and they have access [16:21] to a libraries I I don't think I have in the slide  but they have access to a list of skills and those [16:26] agents are going to basically change skills based  on what they need to do and this is basically what [16:32] they they will they will be kind of changed as  a model identification agent or model validation [16:38] agent and then all of those agents are going  to be executing and act well executing things [16:45] uh and they need to access data and and the data  could be okay I need to have access to the model [16:50] I need to have access to the data I need to have  access to some policies I need to have access to [16:55] whatever think about the person when it needs to  do the job what sort of information documentations [17:00] database is going to get and basically you  have all of those MCP servers that basically [17:05] uh interface with with your uh infrastructure  information and that's basically the agent is [17:12] going to interact and going to execute and then  you have these last layers of the executions when [17:18] you need to execute code when the agent needs  to access data need to run SQL queries when he [17:24] needs to run models when you need to uh access  the model and run some uh inference on top and [17:30] that's where you do the validation that the agent  is going to start execution whatever is a platform [17:36] could be on uh cloud platforms so it could be on  prem whatever is your compute and uh and then yeah [17:43] and and you have uh you store the evidence of  the whatever you computed in this data storage [17:49] right so that's basically it's overall different  layers of what we have and then we we so I only [17:55] have a minute so very quickly with crank agent uh  again the developer submit model information so [18:03] he submit information about what the model is  uh anything he knows about it the agent execute [18:08] against uh again using the skill that have been  created it using the scale creator which used [18:16] the playbook uh related to the the policy and  requirements for doing risk ranking is it spit out [18:22] some output and I propose a rank and rationals and  it goes to the validators and the validators amend [18:28] or accept and um and then there's an approvable  step right so always the same process you a human [18:36] start the task and then an agent execute  it and then a human is taking check taking [18:40] checking and then approve it and that's the  same for validation. So validation validators [18:46] put input there's a bunch of agents that going  to do some orchestrations going it's going to be [18:52] impersonated with skills the checker  skill or tester skills write some content [18:57] and do and build a validation document and uh and  uh yeah so that's and then the same for the review [19:04] agents the validation agents uh they they start  uh um start with the validators and then the AI [19:13] review agents do the view and the validators check  and uh to check everything is fine. So uh yeah so [19:21] and then we have this uh continuous uh periodic  uh continuous monitoring where basically agent [19:32] uh yeah you input traces you do evaluation and the  risk oversight engine is capturing all of those [19:37] traces and and put flies when something is is is  not right. Right. So so very quickly so while main [19:45] for impact so we incre well we have we going much  faster so we have 50% on average reductions for [19:52] doing risk cranking model development validation  and uh and even review monitoring then you move [19:58] from periodic to real time. So using agents you  you have a much faster flow you have standardized [20:05] output because the agent uh they always the same  right. So it's not like you have a bunch on the [20:11] family of validators that may have different maybe  inconsistent way of doing things and then you have [20:18] all the artifact that the agent have been building  on the way which is save and which is kind of a [20:23] audit ready lineage and it's it scales so you can  I mean well up to now up to now most of the things [20:32] that uh the control team was doing is some doing  some sampling of models for doing some check [20:37] right now you don't need to do sampling you just  have those agents that can do the the different [20:42] executions of those uh of those check right  don't have this limitation anymore right all [20:47] right so I'm going to conclude on that slide  so just mentioning we have four building blocks [20:54] we have repeatable executions so thanks  to agents we codify expertise as skills [21:00] that's the key thing when people talk about  agents and agend the agents. But before you [21:04] get those agents, the agents execute on top  of something. If you have the right skill [21:09] and again you can use skill creator from Frontier  model labs that they make this available for us. [21:17] Of course you need to tweak a few things but you  get those skills but they execute those skills [21:21] and uh then you have human accountability out of  the execution of the agents and continuous overite [21:28] right. So uh yeah and just to say faster doesn't  mean less control. It's the goal is really faster, [21:36] more consistent and more traceable model  risk management. So thank you guys for having [21:41] listen listened to me. I'm here till  Thursday. If you have questions on comment, [21:44] I'm going to be take them over and I don't know  if you have time for questions, but I I'll stop