Concern 825 · Working draft · editorial review in progress
G7 Hiroshima Process code of conduct
The Hiroshima AI Process code and reporting framework encourage responsible practices, but voluntary reporting may leave gaps in verification and accountability.
Understanding the concern
Organizations can report how they evaluate risks, handle incidents and improve security. Comparable reports can help others ask better questions. But the company providing the information may choose how to describe its own work, and participation alone does not prove that the practices are effective.
The OECD framework supports reporting against the G7 code of conduct. Think of a restaurant publishing its own hygiene checklist: useful information still needs a way to test important claims. Readers should look for specific methods, evidence, limitations and follow-up rather than treating a completed report as an independent certificate.
An example
A provider reports that it conducts safety tests but gives little detail about what failed or how problems were addressed.
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 source describes a voluntary reporting mechanism. It does not establish mandatory global compliance or independent verification of every submitted claim.
OECD 2025 · Voluntary reporting framework
OECD launches global framework to monitor application of G7 Hiroshima AI Code of Conduct ↗ (opens in a new tab)Comparable organizational reports against a code of conduct. Reporting participation is not independent certification.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
What evidence could independently confirm that the reported safeguards work?
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.