Papers › Reliably detecting model failures in deployment without labels

Reliably detecting model failures in deployment without labels

5 Jun 2025arXiv:2506.05047archive 2025-07-28

Viet Nguyen, Changjian Shui, Vijay Giri, Siddarth Arya, Amol Verma, Fahad Razak, Rahul G. Krishnan

The distribution of data changes over time; models operating operating in dynamic environments need retraining. But knowing when to retrain, without access to labels, is an open challenge since some, but not all shifts degrade model performance. This paper formalizes and addresses the problem of post-deployment deterioration (PDD) monitoring. We propose D3M, a practical and efficient monitoring algorithm based on the disagreement of predictive models, achieving low false positive rates under non-deteriorating shifts and provides sample complexity bounds for high true positive rates under deteriorating shifts. Empirical results on both standard benchmark and a real-world large-scale internal medicine dataset demonstrate the effectiveness of the framework and highlight its viability as an alert mechanism for high-stakes machine learning pipelines.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 12 code samples harvested from 3 repositories linked to this paper: 9 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 5 ran (3 with no instrument failure; 2 where Syntology's instrument failed); found in paper text by Syntology: 5 samples from 2 repositories, 4 ran (0 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

teivng/d3m officialmentioned in paperpytorchSyntology: 7 samples, 5 ran (2 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

12 samples harvested: 9 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
5ran · our draft was wrong
1ran; the contract check could not run
2ran
3unverified

Licence: 2 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

teivng/d3m official repository 7 samples, 5 ran (2 instrument-failed) · 2 unverified
D3MBayesianMonitor d3m/monitors/bayesian_monitor.py ran MIT (permissive) · 31b4c586b6c8ab9b · report fixture: returned D3MBayesianMonitor · level recorded 2026-09-22
TrainConfig in 8 papers d3m/monitors/bayesian_monitor.py ran MIT (permissive) · e31bb08debb2367d · report fixture: returned TrainConfig · level recorded 2026-09-22
get_class_from_string d3m/monitors/bayesian_monitor.py ran · our draft was wrong MIT (permissive) · 24c4d57d39e03345 · report fixture: signature class_string:str/0/str · returned type · level recorded 2026-09-22
sample_from_dataset d3m/monitors/bayesian_monitor.py ran · our draft was wrong MIT (permissive) · 9fcb4375a26ac02b · report fixture: signature n_samples:int/0/int, dataset:SimpleDataset/0/?, replace:bool/0/bool · returned tuple · level recorded 2026-09-22
temperature_scaling in 5 papers d3m/monitors/bayesian_monitor.py ran · honoured contract fingerprinted MIT (permissive) · 6688a7f57e8828e0 · report fixture: signature logits:Tensor/2/float, temperature:float/0/float · returned Tensor · level recorded 2026-09-22
D3MAbstractModel d3m/monitors/bayesian_monitor.py unverified MIT (permissive) · 745669490b50fd4f · report
D3MMonitor d3m/monitors/bayesian_monitor.py unverified MIT (permissive) · 99a9a8040630f606 · report
fengliu90/DK-for-TST found in paper text by Syntology 3 samples, 2 ran (2 instrument-failed) · 1 unverified
MMDu in 5 papers utils.py ran · our draft was wrong MIT (permissive) · b2fd0117a1785dcf · report fixture: signature Fea:Tensor/2/float, len_s:int/0/int, Fea_org:Tensor/2/float, sigma:float/0/float, sigma0:float/0/float, epsilon:float/0/float, is_smooth:bool/0/bool, is_var_computed:bool/0/bool, use_1sample_U:bool/0/bool · returned tuple · level recorded 2026-09-22
mmd2_permutations utils.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 123d5b309dfd538f · report fixture: signature K:Tensor/2/float, n_X:int/0/int, permutations:int/0/int · returned tuple · level recorded 2026-09-22
TST_MMD_u utils.py unverified MIT (permissive) · ec24b4387148fe67 · report
a7b23/H-Divergence found in paper text by Syntology 2 samples, 2 ran (2 instrument-failed) · 0 unverified
JSV_Gaussian utils.py ran · our draft was wrong no licence file found · pointer only · 9351e8786754a459 · report fixture: returned tuple · level recorded 2026-09-22
JSV_Gaussian_u utils.py ran · our draft was wrong no licence file found · pointer only · a42e81244edb9510 · report fixture: signature Fea:ndarray/2/float, len_s:int/0/int, n_components:int/0/int, vtype:str/0/str · returned float32 · level recorded 2026-09-24

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

3 assemblies on this paper: 3 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

3 sibling assemblies for D3M (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for D3M (graph method: D3M). 7 bricks; individually on a fixture: 5 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. D3MBayesianMonitor entry · level 1 · ran · 31b4c586b6c8ab9b
  2. D3MMonitor helper · level 0 · unverified · 99a9a8040630f606
  3. temperature_scaling helper · level 1 · ran · honoured contract · 6688a7f57e8828e0
  4. D3MAbstractModel model · level 0 · unverified · 745669490b50fd4f
  5. TrainConfig helper · level 1 · ran · e31bb08debb2367d
  6. get_class_from_string helper · level 1 · ran · our draft was wrong · 24c4d57d39e03345
  7. sample_from_dataset helper · level 1 · ran · our draft was wrong · 9fcb4375a26ac02b

harvested Assembly for D3M (graph method: D3M). 5 bricks; individually on a fixture: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. TST_MMD_u entry · level 0 · unverified · ec24b4387148fe67
  2. MMDu model · level 1 · ran · our draft was wrong · b2fd0117a1785dcf
  3. mmd2_permutations helper · level 1 · ran; the contract check could not run (RAISES) · 123d5b309dfd538f
  4. Pdist2 helper · level 1 · ran · honoured contract · 0b62387de45ba23b
  5. h1_mean_var_gram helper · level 0 · unverified · 511ae80b14ef8561

harvested Assembly for D3M (graph method: D3M). 2 bricks; individually on a fixture: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 3 siblings

  1. JSV_Gaussian entry · level 1 · ran · our draft was wrong · 9351e8786754a459
  2. JSV_Gaussian_u helper · level 1 · ran · our draft was wrong · a42e81244edb9510

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2506.05047") returns these assemblies with each brick's role and wiring (how to connect).

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections