liveBook · Manning

Robustness

Robustness is the ability of a system or model to maintain acceptable behavior or performance despite variations, disturbances, faults, or challenging conditions.

How 7 Manning books explain it

Machine Learning System Design

A software quality property of continuing to operate and produce some result despite errors or abnormal conditions, even when the result may be inaccurate.

How it is used
Guides error-handling choices by mistake cost and assesses whether ML outputs remain dependable under small input changes.
How deep it goes
Defines the correctness tradeoff and describes perturbation checks, without prescribing universal tolerance thresholds.
Examples
Contrasts an AR mask with a self-driving car and uses changing antifraud classifications to illustrate release instability.
What you can do after
Evaluate/understand it by choosing error behavior according to mistake costs and checking whether small perturbations disrupt predictions.

Read how Machine Learning System Design explains robustness →

Delivering Machine Learning Projects: From design to deployment

Robustness is the ability of a system to maintain acceptable performance across specified circumstances and perturbations.

How it is used
Uses robustness testing as evidence for acceptance to service and safer deployment decisions.
How deep it goes
Defines characterization and testing across circumstances, stopping short of specifying technical test methods.
Examples
Uses generative art, generative text, and facial recognition to compare intended-function and failure harms.
What you can do after
Evaluate/understand system behavior under specified circumstances and inform acceptance-to-service and mitigation decisions.

Read how Delivering Machine Learning Projects: From design to deployment explains robustness →

Sutskever's List

Robustness is a model's ability to maintain reliable behavior under perturbations, distribution changes, and atypical inputs.

How it is used
Tests whether benchmark success survives adversarial inputs and real-world distribution shifts.
How deep it goes
Identifies adversarial and deployment failures but does not develop robustness mechanisms or detailed evaluation procedures.
Examples
Uses ImageNet scores, imperceptible perturbations, and Google Photos’ gorilla-labeling incident.
What you can do after
Evaluate claims of human-level performance against adversarial inputs and atypical real-world cases.

Read how Sutskever's List explains robustness →

Statistics Every Programmer Needs

Model robustness is the ability of a predictive model to maintain reliable performance across variation in data or conditions.

How it is used
Monitors process stability, detects deviations, and supports corrective action through visual quality-control charts.
How deep it goes
Explains control limits, means, standard deviations, chart selection, and implementation, but does not develop predictive-model robustness.
Examples
Uses orange-juice can defects, range variation, defects per unit, and synthetic intervals between rare defects.
What you can do after
Diagnose process instability with control charts and interpret points, trends, limits, and variation for corrective action.

Read how Statistics Every Programmer Needs explains robustness →

Causal AI

Robustness is the property of maintaining acceptable model behavior when deployment conditions differ from training conditions.

How it is used
Frames robustness as a deployment requirement and a sensitivity check for causal estimates.
How deep it goes
Explains overfitting, underspecification, data drift, and confounding sensitivity, but does not develop model-training internals.
Examples
Uses elevation and temperature across cities, plus a DoWhy heatmap that varies unobserved-confounder influence.
What you can do after
Diagnose causal-estimate sensitivity with DoWhy by introducing an unobserved common cause and inspecting changed effect estimates.

Read how Causal AI explains robustness →

The AI Pocket Book

How it is used
Improves software reliability by making validation central to development rather than a secondary task.
How deep it goes
Explains robustness procedurally through edge-case analysis, unit tests, persistent checks, and testing tradeoffs.
Examples
Uses edge-case tests, print statements, small code units, and validation-driven team workflows as concrete examples.
What you can do after
Apply it via test-driven development by designing tests for failure cases and keeping valuable checks in the codebase.

Read how The AI Pocket Book explains robustness →

Generative AI in Action

Robustness is the ability of a machine-learning model to maintain acceptable behavior when inputs vary, are perturbed, or include difficult cases.

How it is used
Tests LLM resilience against adversarial, varied, and edge-case inputs during red-teaming and enterprise evaluation.
How deep it goes
Connects robustness to adversarial generation, data augmentation, and edge-case checks, without detailing metrics or remediation procedures.
Examples
Uses TextAttack, NL-Augmenter, edge-case inputs, and a SLURM pipeline evaluating Llama 2, Baichuan2, Mistral, and other models.
What you can do after
Diagnose robustness risks by generating adversarial inputs and comparing model behavior across varied and difficult cases.

Read how Generative AI in Action explains robustness →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.