Notifications
Clear all
Topic starter
20/08/2026 5:21 pm
TL;DR: AI regulations such as the EU DSA and U.S. transparency proposals are pushing companies to explain how models produce outcomes, with Fiddler arguing that black-box ML will not satisfy emerging audit and user-rights expectations. The governance gap is not just technical opacity, but the absence of continuous model monitoring, documented explanations, and decision traceability that modern AI oversight now demands.
NHIMG editorial — based on content published by Fiddler: AI regulations are here. Are you ready?
Questions worth separating out
Q: How should organisations govern AI models that cannot fully explain their outputs?
A: Start by requiring documented decision rationale, monitoring evidence, and accountable ownership for each model.
Q: Why do black-box AI models become a compliance problem in regulated sectors?
A: They become a compliance problem when the organisation cannot justify outputs to auditors, regulators, or affected users.
Q: How do teams know if AI observability is actually working?
A: It is working when teams can show which change caused a quality shift, which dataset surfaced the issue, and whether the regression was contained before users were affected.
Practitioner guidance
- Establish model explanation requirements Define which decisions require local and global explanations, then make those requirements part of model approval for regulated use cases and identity-adjacent outcomes.
- Operationalise continuous model monitoring Track drift, bias indicators, and unusual prediction patterns across training and production so governance teams can review changes before users or auditors do.
- Create evidence-ready governance records Store model cards, monitoring outputs, review decisions, and remediation notes together so audit requests can be answered without reconstructing the history from scratch.
What's in the full article
Fiddler's full blog covers the operational detail this post intentionally leaves for the source:
- A deeper explanation of how algorithmic transparency maps to regulatory compliance for specific AI use cases.
- Model observability and explainability architecture details for teams building production monitoring workflows.
- Examples of how Shapley Values and Integrated Gradients support root-cause analysis in model governance.
- The article's discussion of how to align MLOps practices with emerging legal expectations for AI decisions.
👉 Read Fiddler's analysis of AI regulations, explainability, and model governance →
AI explainability and model governance are changing fast for teams?
Explore further
20/08/2026 6:12 pm
Algorithmic opacity is now a governance risk, not just a model limitation. When organisations cannot explain why a model produced a result, they also cannot reliably defend that result to auditors, regulators, or affected users. That creates a control gap analogous to poor identity traceability, where decisions exist without accountable evidence. Practitioners should treat explainability as a governance baseline for any AI system that influences regulated or identity-adjacent outcomes.
A question worth separating out:
Q: What is the difference between explainable AI and model governance?
A: Explainable AI focuses on understanding why a model made a decision. Model governance is broader and covers ownership, review, monitoring, documentation, approval, and accountability across the full lifecycle. A model can be explainable but still poorly governed if the organisation cannot prove who approved it, how it is monitored, or what happens when behaviour changes.
👉 Read our full editorial: AI explainability pressure is reshaping model governance requirements
