#pipeline
12 approved public terms with this tag.
Pipeline Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for automated data and model workflow. It uses slice metrics, representative data, and reviewer notes so teams can surface fairness risks while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Calibration Curve is a ml diagnostic that compares predicted confidence with observed outcomes for automated data and model workflow. It uses bucketed predictions, reliability diagrams, and threshold analysis so teams can make confidence scores useful while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Data Split is a ml experimental control that separates examples for training, validation, and testing for automated data and model workflow. It uses randomization rules, leakage checks, and seed tracking so teams can measure generalization honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Drift Monitor is a ml monitor that detects when data or predictions no longer match the training baseline for automated data and model workflow. It uses statistical tests, time windows, and alert thresholds so teams can respond before quality drops while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Embedding Refresh is a ml index workflow that updates vector representations after source data changes for automated data and model workflow. It uses batch jobs, backfills, and index validation so teams can keep retrieval results current while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Evaluation Harness is a ml test system that runs repeatable checks against model behavior for automated data and model workflow. It uses fixtures, metrics, thresholds, and regression reports so teams can compare releases with evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Feature Store is a ml service that serves consistent features to training and inference for automated data and model workflow. It uses versioned feature definitions, freshness checks, and access policies so teams can avoid training-serving skew while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Hyperparameter Sweep is a ml optimization process that searches over model settings to improve a target metric for automated data and model workflow. It uses bounded search spaces, trial tracking, and early stopping so teams can find better configurations while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Label Review is a ml quality workflow that checks annotations for consistency and usefulness for automated data and model workflow. It uses agreement metrics, reviewer queues, and adjudication so teams can improve supervised learning data while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Model Card is a ml documentation artifact that summarizes intended use, limits, and evaluation evidence for automated data and model workflow. It uses dataset notes, metric tables, and risk statements so teams can publish model behavior honestly while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Provenance Ledger is a ml record that tracks where data came from and how it changed for automated data and model workflow. It uses hashes, source labels, and transformation history so teams can audit model inputs reliably while keeping evidence, reliability, and public-safe operational boundaries clear.
Pipeline Training Checkpoint is a ml recovery artifact that saves model state during learning for automated data and model workflow. It uses weights, optimizer state, and run metadata so teams can resume or inspect training safely while keeping evidence, reliability, and public-safe operational boundaries clear.