Use case 4 · Bayesian accuracy monitoring
Watching an AI tool through a vendor update
The pattern
AI tools change when vendors update them. A fixed set of questions with known answers, asked every month, shows when accuracy drops.
- Question
- Would we notice if an AI tool's answers got worse?
- Lane
- Advice relied on
- Basis
- Reporting and standard practice
What METRIS does
- Ask a fixed bank of questions with known correct answers every month
- Estimate accuracy with an interval and alert when it is credibly below target
- Hold decisions that rely on the tool while an alert is open
One run: accuracy through a vendor update
Accuracy drops from 95% to 85% at the month-5 update. With 40 questions a month, the alert fires in month 6.
Method
- Accuracy before update
- 95%
- After update
- 90%, 85% or 80%
- Questions per month
- 40 or 100
- Runs
- 1,000 per setting
One wrong answer proves little. A posterior probability says how sure we are that accuracy fell below what the business needs, and it updates every month.
Detection by size of drop and question bank
A drop to 85% is detected in 93% of years with 40 questions a month and 99.8% with 100. A drop to exactly the 90% target is still flagged in 25% and 33% of years, because each monthly check adds a chance of a false alarm.
Reproducibility
Correct answers are binomial; posteriors are Beta with a uniform prior. Random seed 20261013; Python with NumPy 2.5.3 and SciPy.
Sources
This pattern is not based on any single record. Its figures come from the model stated above.
A statistical study of a pattern, not of any event. It identifies no organization or person. Simulated figures use synthetic data; published figures are industry-wide.