Concern 166 · Working draft · editorial review in progress

Compromised base model

A compromised base model is a starting model that has been deliberately altered to behave improperly in some conditions.

Understanding the concern

Organizations often build on a model supplied by someone else. A hidden change can travel into many downstream products, especially if ordinary tests do not trigger it. The problem may lie in the training process, the model files, or a later substitution.

This differs from a model that simply makes errors or reflects biased data. Compromise implies unauthorized interference. Checking the supplier and file history helps establish origin, while behavioral testing addresses what the model does; neither replaces the other.

An example

Several builders use the same faulty component, and each finished product inherits a hidden weakness.

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.
Training
The process of using examples to shape how an AI model behaves. Learning patterns from material does not establish that the material is true or fair.

Evidence and its limits

NIST describes backdoor mechanisms and secure development practices. The example is a supply-chain scenario, not an allegation against a supplier.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

How do we check both the origin and behavior of the model we build 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.

Stewardship

Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.

Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.

Ask together: What are we responsible for caring for over time?

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?

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?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Major · 4/5
Likelihood
Widely observed · 4/5
Time horizon
Now
Register risk score
16
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.

Explore a proposed use of AI →