In plain English
This page is part of the technical reference. It keeps the expert detail but starts with a plain-language summary for first-time readers.
- Why this matters: AI risk can come from the whole arrangement, not one obvious model.
- What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
- Technical version below: the expert terminology remains available and is linked through the glossary.
Model Diversity, Monoculture, and Governed Variation
Direct answer
Diversity can be protective, but only when governed. Monoculture creates shared blind spots. Ungoverned diversity creates chaos, hidden variants, and accountability gaps.
The balance
Useful diversity means genuinely different data, model families, objectives, evaluators, routes, and deployment policies. It can reduce correlated failure and preserve rare cases.
But untracked variants can create shadow AI. If no one knows which model is active, what data it uses, who approved it, or how to roll it back, diversity becomes opacity.
Monoculture risk
Monoculture appears when many systems depend on the same model family, evaluatorA system that judges whether an AI output or candidate is acceptable. Open glossary definition, benchmark, training data, supplier, routing library, or safety rubric. The apparent independence is fake because the failure modes are correlated.
Ungoverned diversity risk
Ungoverned diversity appears when many variants exist without shared evidence requirements, model cards, lineageThe parent-child history of models, adapters, datasets, or releases. Open glossary definition, retirement triggers, access control, and incident response.
Governed diversity controls
- multiple meaningful model families or data sources where practical;
- independent evaluator families;
- model cards and datasheets;
- lineage and registry records;
- fairness, robustness, rare-case, and red-team evidence;
- canary and rollbackReturning a system to an earlier known state. Open glossary definition plans;
- retirement criteria;
- clear owners for each variant.
What to watch for
- all judges share the same supplier or training data;
- every fallback routes to the same underlying model family;
- many variants have different names but near-identical behavior;
- shadow deployments outside the registry;
- one routing library controls all traffic;
- the same benchmark drives every promotion.