Concern 831 · Working draft · editorial review in progress
Interoperability of AI risk-management frameworks
Interoperability between AI risk frameworks means being able to compare and reuse useful work across them without pretending their requirements are identical.
Understanding the concern
Organizations may face several frameworks using different names for similar tasks, such as identifying harms, testing systems and monitoring results. A good comparison can reduce duplicated paperwork and make gaps easier to see. A poor comparison can hide a requirement that exists in one framework but not another.
OECD guideposts identify common ideas that can support comparison. Think of translating between two measuring systems: a conversion helps only when you know what each measurement means. Mapping one framework to another is not automatic legal compliance. The important test is whether evidence and safeguards remain adequate for the actual people and use involved.
An example
A supplier says its compliance with one voluntary framework automatically satisfies another country's mandatory AI law.
Illustrative unless identified as a documented case.
Words in plain English
- AI
- Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.
Evidence and its limits
The guideposts support common understanding and comparison. They do not make different legal regimes equivalent or create mutual recognition of every audit.
OECD 2023 · Framework comparison
Common guideposts to promote interoperability in AI risk management ↗ (opens in a new tab)Common concepts and processes help comparison but do not make laws equivalent.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
Which requirements genuinely match, and which still need separate evidence or action?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Accountability
Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.
Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.
Ask together: Who will answer for the outcome and help put things right?
Prudence
Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.
Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.
Ask together: What is a careful next step, and when should we stop or change course?
Unity
Unity means working toward shared purposes while making room for real differences. It does not require everyone to have the same experience, beliefs, or opinion.
Look for a goal people can share, then explore disagreements about how to reach it. Make sure quieter or less powerful voices can influence the result.
Ask together: What purpose can we share while respecting our differences?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.