Concern 199 · Working draft · editorial review in progress
Model cards missing or shallow
Missing or shallow model cards leave users without a useful description of a model's intended uses, tests, and limits.
Understanding the concern
A model card is structured documentation that accompanies a model. It can describe the conditions in which it was evaluated and the uses it was designed to support. Without that information, a buyer may mistake a broad performance claim for evidence that the model fits their situation.
A card can exist yet still be unhelpful if it is outdated, vague, or silent about relevant groups and failures. Documentation should identify the model version and distinguish tested results from aspirations. A polished document does not substitute for independent evidence.
An example
An appliance comes with a sales brochure but no clear account of its operating limits.
Illustrative unless identified as a documented case.
Words in plain English
- Model
- The learned part of an AI system. It uses patterns found during training to produce an answer or prediction.
Evidence and its limits
The original model-card framework proposes structured reporting; it does not establish the quality of every current vendor's documentation.
Mitchell and colleagues · FAT* 2019 · Research proposal
Model Cards for Model Reporting ↗ (opens in a new tab)Proposes documentation of intended use, evaluation conditions and performance; a card's existence is not proof of quality.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
Does the documentation tell us where this exact model was tested and where it should not be relied on?
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.
Trustworthiness
Trustworthiness means giving people good reasons to rely on you. It grows when promises, actions, and evidence line up. With AI, a friendly voice or a famous brand is not enough: people need to know what was checked and what could still go wrong.
In practice, keep promises small enough to test, record mistakes, and tell people when the tool's limits affect them. If a service promises human review, make sure a person really has time and authority to review it.
Ask together: What would give the people affected a sound reason to trust this use?
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?
Truthfulness
Truthfulness means making claims that match the evidence and being clear about what we do not know. It includes correcting mistakes rather than protecting a polished story.
Check sources, label guesses, and distinguish a trial result from a proven benefit. If AI helped produce a claim, someone still needs to take responsibility for checking it.
Ask together: What can we honestly say, and what still needs checking?
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.