#Risk Management
Articles about Risk Management — exploring patterns, best practices, and real-world implementations in production systems.
11 posts tagged with risk management. ← Blog home
Every model in this series was a tool for one ultimate purpose: understanding and controlling risk. Risk management is where financial engineering meets reality — where elegant models confront messy markets, fat tails, and the uncomfortable truth that the most dangerous risks are the ones your model didn't consider. This closing post covers how risk is measured and managed in practice, and how to build financial models responsibly, knowing they will eventually be wrong.
Risk management is the purpose every model served. Value at Risk and its tail-hiding flaw (so expected shortfall), fat tails, hedging with the Greeks, market microstructure as a systems problem, and the overriding lesson: models are approximations that will eventually be wrong — so respect the tails and stay humble. (Educational, not financial advice.)
If the valuation engine answers "what is this worth?", the risk engine answers the question that actually keeps institutions solvent: "what could go wrong, and how badly?" Risk engines turn the theory of VaR, stress testing, and scenario analysis into production systems that run across whole portfolios — and AI both accelerates them and extends them into risks that were previously too unstructured to quantify. This post is about building the risk core.
The risk engine answers what keeps institutions solvent: what could go wrong, and how badly? Building VaR, stress testing, and scenario analysis in production, how AI accelerates (surrogate-powered scenarios) and extends (unstructured risks) — and the danger it carries: AI can make risk engines more confident and more wrong at once. (Educational, not financial advice.)
Every idea in this series is worthless until someone builds the function that runs it. The most common failure in AI governance isn't picking the wrong framework — it's never getting past the framework to an operating capability, or building such a heavy one that the organization routes around it. This closing post is a practical path from zero: what to build first, how to make governance an enabler rather than a blocker, and how to grow the function as AI adoption grows. It turns the series into a plan.
Every idea in the series is worthless until someone runs it. A practical path from zero: start with visibility (inventory, then risk-tier, then a minimal owner-assigning policy), build controls highest-leverage-first in runnable layers, and make governance an enabler — the easy path — so it accelerates trustworthy AI rather than blocking it.
Governance that stops at deployment governs the wrong moment. An AI system's real behavior — and its real risks — emerge in production, over time, as the world drifts and users do things no test anticipated. Post-deployment governance is the discipline of watching systems in the wild, catching when they go wrong, and maintaining a clear line of accountability for what they do. This post is about governance as an ongoing operational practice, not a launch checklist.
Governance that stops at deployment governs the wrong moment — risk emerges in production as the world drifts and users find the edges. Monitoring the governance-relevant signals (drift, continuous bias, safety) with thresholds tied to action, plus accountability for a system's whole life: durable owners, AI incident response, traceability, and redress.
The EU AI Act is the world's first comprehensive AI law, and for engineers it is neither as scary nor as vague as it first appears. Underneath the legal language is a risk-based structure that translates into a concrete checklist of engineering obligations — and most of them are things a good governance program (this series) already does. This post is about reading the Act the way an engineer should: not as compliance theater, but as a specification of controls you can implement.
The EU AI Act is risk-based, so your first job is classification — then the high-risk obligations translate into a concrete checklist most mature governance already does: risk management, data governance, documentation, logging, human oversight, robustness, conformity assessment. Read the law as a specification of controls, not compliance theater.
Two questions separate real AI governance from theater: can you stop a model that fails its checks from reaching production, and can you prove, after the fact, that the checks were done? The first is an evaluation gate; the second is evidence. Together they turn governance from a set of good intentions into something enforceable and auditable. This post is about the mechanics of gating AI systems on quality and automatically capturing the proof that it happened.
Two questions separate governance from theater: can you stop a model that fails its checks, and can you prove the checks happened? Evaluation gates that fail closed (with teeth and legitimacy), and evidence — the automatic audit trail that governance-as-code produces for free — for regulators, auditors, and incident reconstruction.
A governance policy written in a PDF is a suggestion; a policy written as code is a control. The difference between the two is the difference between hoping teams comply and knowing they do, because the policy runs automatically and blocks what violates it. Governance as code applies the lessons of infrastructure-as-code and policy-as-code to AI governance — turning principles into executable, version-controlled, automatically-enforced checks. This post is about making governance something the system does, not something a document asks for.
A policy in a PDF is a suggestion; a policy as code is a control. Governance as code makes policy imperative — version-controlled, executable rules that run automatically at deploy, at runtime, and at registration, failing closed on what matters. What you can encode as gates, and what still needs human judgment.
Governing a model that answers questions is hard; governing one that takes actions is a different problem entirely. Agentic AI — systems that plan, call tools, and execute steps toward a goal with limited human oversight — moves AI from producing outputs to producing consequences. The governance frameworks built for predictive models and even for chatbots don't fully cover an agent that can send an email, move money, or modify a system. This post is about the controls that specifically matter when AI can act.
Governing a model that answers is hard; governing one that acts is a different problem — a wrong action escapes into the world. Why agents break the usual frameworks, and the controls that bound authority and consequences: least privilege, human-in-the-loop for consequential actions, bounded execution, agent identity, and fail-safe defaults.
Banks have managed the risk of models being wrong for decades, under a formal discipline called model risk management. AI didn't invent the problem of a model that's confidently incorrect — it industrialized it. The good news is that a mature, battle-tested framework already exists, and adapting it to machine-learning and LLM systems is one of the highest-leverage moves in AI governance. This post is about treating "the model might be wrong" as a managed risk, not a hope.
Banks have managed 'the model might be wrong' for decades under model risk management (SR 11-7). Its lifecycle — documented development, independent validation, risk-tiered approval, ongoing monitoring, revalidation/retirement — maps onto AI, which then stresses it with opacity, un-inspectable foundation models, open-ended generation, and scale.
AI governance fails most often not because an organization lacks principles, but because nobody owns them. Fairness, safety, and accountability are everyone's job in the abstract and no one's job in practice, so they fall through the cracks between data science, legal, risk, and engineering. This series is about governance as an operating model you can actually run — and it starts with the unglamorous foundation: clear ownership, defined roles, and the mechanisms that turn good intentions into enforced practice.
AI governance fails from an ownership gap, not an absence of principles. The operating model: decision rights and accountability via the three lines of defense, named roles laddering to an executive owner, and the mechanisms that give them teeth — an AI system registry, risk tiering, and lifecycle gates.
Turning the four functions of the NIST AI Risk Management Framework — GOVERN, MAP, MEASURE, MANAGE — into something an engineering team can actually run: a risk taxonomy for LLM apps, a versioned risk register in code, and the eval hooks that keep MEASURE honest.
Make the NIST AI Risk Management Framework actionable: the Govern/Map/Measure/Manage functions in your own words, a risk taxonomy for LLM apps, and a versioned risk register (YAML/Python) capturing per-use-case risks, likelihood/impact, mitigations, and owners.
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse the blog or explore related topics using the tag cloud above.