This glossary gathers the vocabulary that appears most often in modern AI projects. Entries are grouped in five sections—core terms; model families and techniques; infrastructure and operations; safety, risk, and compliance; and metrics and evaluation. The aim is plain language without shortcuts. Where a term has several competing definitions, the entry explains the version used in this book and notes common alternatives.
21.1 Core Terms
- Artificial Intelligence (AI): A field of computing that builds systems able to perform tasks that typically require human cognition—recognizing patterns, making predictions, understanding language, or deciding among options—using data and algorithms rather than fixed, step‑by‑step rules.
- Machine Learning (ML): A subset of AI. Instead of writing explicit rules, developers supply examples and let algorithms learn rules that map inputs to outputs. Learning can be supervised (with labeled answers), unsupervised (structure is inferred), or reinforced (choices earn rewards or penalties).
- Model: A mathematical object—usually a large collection of numbers (weights)—that transforms inputs into outputs. Training adjusts those numbers so the model does useful work (e.g., classify an email, generate text, detect a defect).
- Algorithm: The recipe used to build or use a model. “Training algorithm” describes how weights are updated from data (e.g., stochastic gradient descent). “Inference algorithm” describes how outputs are produced from a trained model (e.g., sampling tokens from a language model).
- Parameters / Weights: The adjustable numbers inside a model. Training tunes them; inference uses them to produce answers. “A 70‑billion‑parameter model” refers to its size, not its quality.
- Feature: A measurable property of an input used by a model. For tabular data, a feature might be “days since last purchase.” For text and images, features are derived automatically inside neural networks.
- Token: A unit of text used by language models. Tokens are often pieces of words; “unbelievable” might be split into “un‑”, “believ‑”, and “‑able.” Models read and produce tokens, not characters.
- Tokenization: The process that converts raw text into tokens and back. Tokenization affects cost, context length, and behavior. Different models use different tokenizers.
- Vocabulary: The set of all tokens a model understands. Unlike a human vocabulary, this includes word pieces and punctuation; it may also include special tokens that control formatting or behavior.
- Context Window: The maximum number of tokens a language model can consider at once—the sum of input tokens and generated tokens. Larger windows allow longer documents and histories but cost more to process.
- Prompt: The input text (and, for multimodal models, images or other signals) given to a model to guide its behavior. Prompts can include instructions, examples, or structured fields. Prompts are not programs; they are inputs that a statistical model interprets.
- System Prompt: A fixed set of instructions that sets the model’s role and policy for a session (e.g., “Answer concisely and cite sources”). It sits “above” user prompts.
- Few‑Shot / Zero‑Shot: Zero‑shot means asking a model to perform a task using only instructions. Few‑shot adds a small number of examples in the prompt to show the desired pattern or format.
- Inference: Using a trained model to produce outputs for new inputs. Inference is the runtime phase: answering a question, classifying a record, generating code.
- Training: Adjusting model weights so that outputs improve on a set of examples. Training consumes compute and data; the result is a model checkpoint.
- Pretraining: The initial large‑scale training stage (often on general data) that teaches broad patterns—grammar, common facts, visual features—before any domain adaptation.
- Fine‑Tuning: An additional, smaller training stage that specializes a pretrained model to a domain, tone, format, or task (customer support answers, a product’s coding style).
- Instruction Tuning / Supervised Fine‑Tuning (SFT): Fine‑tuning on paired instruction–response examples to make a model follow directions and produce helpful, safe, and concise answers.
- Reinforcement Learning from Human Feedback (RLHF): A training method that collects human preferences among model outputs and uses them to teach the model which responses are better. A reward model learns to score outputs; the base model is nudged toward higher‑scoring behavior.
- Direct Preference Optimization (DPO): An alternative to RLHF that trains directly on pairwise preferences without training a separate reward model, simplifying the pipeline.
- Alignment: The extent to which a model’s behavior matches the goals, rules, and values set by its operators. Alignment is achieved through data selection, training choices, prompts, guardrails, and oversight.
- Hallucination / Fabrication: A model output that is fluent but incorrect or unsupported by evidence. The term is informal; a clearer phrase is “unsupported claim.” Guarding against it requires grounding and validation, not just bigger models.
- Grounding: Constraining a model to answer using approved sources and to show citations or other evidence. Grounded answers can be checked; free‑form claims cannot.
- Retrieval: Fetching relevant documents or records from a knowledge base to use as context for generation or decision‑making.
- Retrieval‑Augmented Generation (RAG): A pattern that retrieves relevant passages and supplies them to a language model as context so that answers reflect current, approved information.
- Agent: A system that uses a model to plan and act in steps—often calling tools, updating memory, and checking results—toward a goal. An agent is “model + planner + tools + rules,” not just a chat interface.
- Tool / Function Calling: A controlled way for a model to request actions—query a database, fetch a document, calculate a value—by producing structured arguments to predefined functions that the orchestrator executes.
- Planner / Executor: In an agent, the planner proposes steps; the executor runs tools and returns results. Splitting these reduces risk and simplifies debugging.
- Orchestration: The software layer that structures prompts, manages retrieval, validates outputs, calls tools, enforces permissions, and logs traces.
- Memory (Short‑Term / Long‑Term): Short‑term memory is the conversation or task history kept in the context window. Long‑term memory stores summaries or facts between sessions in a database or vector index.
- Corpus: The collection of documents you rely on—manuals, policies, tickets, emails, code—that feed retrieval or training.
- Dataset: A structured collection of examples used for training or evaluation. Good datasets include provenance, labels, and definitions of success.
- Label / Annotation: A human‑supplied answer or tag for an example. Labels can be exact (the correct field value) or judgments (which draft is better).
- Weak Supervision: Imperfect labels created automatically—via rules, heuristics, or distant sources—used to scale training when perfect labels are expensive.
- Synthetic Data: Data generated by models or simulations to augment scarce examples. Useful for rare cases; risky if it reinforces errors or biases.
- Generalization: A model’s ability to perform well on new, unseen data—not just the training examples.
- Overfitting: When a model memorizes training quirks instead of learning patterns, performing poorly on fresh data.
- Distribution Shift / Drift: When the data seen in production differs from the data used in training (new product names, new formats, new user intents), causing performance to change.
- Benchmark: A standardized test used to compare models. Useful for one skill under fixed conditions; not a full representation of your workflows.
21.2 Model Families and Techniques
- Linear Models: Simple models that combine input features linearly. Easy to train and explain. Baselines for many tabular problems.
- Logistic Regression: A linear model for classification. Outputs probabilities via a logistic function. Despite the name, it is a classifier, not a regression in the everyday sense.
- Decision Tree: A flow‑chart model that splits data by rules (“if amount > X then …”). Intuitive and interpretable; can overfit without pruning.
- Random Forest: An ensemble of decision trees trained on random subsets. Reduces overfitting; good accuracy on many tabular tasks.
- Gradient Boosting (e.g., XGBoost, LightGBM, CatBoost): Builds trees sequentially, each correcting the errors of the previous ones. Strong performance on structured data.
- Support Vector Machine (SVM): A classifier that finds a boundary maximizing the margin between classes. Effective in moderate‑dimension spaces; less used for very large datasets.
- Naïve Bayes: A simple probabilistic classifier that assumes feature independence. Fast and surprisingly effective for some text problems.
- k‑Nearest Neighbors (k‑NN): Classifies or regresses based on the closest examples in feature space. Requires efficient indexing; sensitive to scaling.
- Clustering (k‑Means, Hierarchical): Unsupervised grouping of similar items. Used for exploration, customer segmentation, or deduplication.
- Topic Models (e.g., LDA): Unsupervised methods that uncover themes in document collections. Partially superseded by embedding‑based methods.
- Hidden Markov Model (HMM): A probabilistic model for sequences with hidden states. Classic for speech and simple time series; often replaced by neural models.
- Collaborative Filtering / Matrix Factorization: Recommendation methods that factorize user–item interactions into latent factors; represent tastes and attributes in vector spaces.
- Neural Network: A model built from layers of simple functions (neurons) whose weights are learned. Flexible enough to approximate complex mappings.
- Perceptron / Multilayer Perceptron (MLP): The perceptron is a single‑layer neural classifier; an MLP stacks fully connected layers to model nonlinear patterns.
- Convolutional Neural Network (CNN): A neural network that uses “filters” to detect local patterns; central to image recognition and also used in audio and some text tasks.
- Recurrent Neural Network (RNN), LSTM, GRU: Sequence models that process inputs one step at a time while carrying state. LSTM and GRU units mitigate vanishing gradients. Largely supplanted by transformers for language, though still used in smaller on‑device models.
- Attention: A mechanism that lets models weigh which parts of the input matter for the current prediction. Key to modern language and vision models.
- Transformer: The dominant neural architecture for language and many multimodal tasks. Uses attention to process sequences in parallel. Underlies most large language models (LLMs).
- Encoder / Decoder / Encoder–Decoder: Transformer variants: an encoder reads inputs (useful for classification, embeddings); a decoder generates outputs (useful for text generation); encoder–decoder pairs are common in translation and vision–language tasks.
- Language Model (LM): A model trained to predict the next token (causal) or fill masked tokens (masked LM). Causal LMs are used for generation; masked LMs are common for embeddings and classification.
- Causal vs. Masked LM: Causal LMs read left‑to‑right and generate text; masked LMs see the whole sentence with some tokens hidden and learn to fill them in.
- Diffusion Model: A generative model that learns to remove noise step by step, producing images or audio from random noise guided by text or other signals.
- Variational Autoencoder (VAE): A model that compresses inputs into a latent space and reconstructs them. Useful for anomaly detection and generative tasks with smooth latent controls.
- Generative Adversarial Network (GAN): Two networks—generator and discriminator—trained in a contest. Historically strong for images; less common for text.
- Mixture of Experts (MoE): A model with many “expert” sub‑networks where only a subset is active per input. Increases capacity without proportional compute at inference.
- Multimodal Model: A model that jointly processes more than one modality—text + image, text + audio, etc.—to answer questions, describe scenes, or follow instructions grounded in visuals.
- Vision–Language Model (VLM): A multimodal model specialized for tasks like image captioning, visual question answering, and document understanding.
- Automatic Speech Recognition (ASR): Models that transcribe audio into text.
- Text‑to‑Speech (TTS): Models that synthesize speech from text in specific voices or styles.
- Embedding Model: A model that maps text, images, or other inputs into vectors (lists of numbers) so that semantic similarity can be measured by distance.
- Bi‑Encoder vs. Cross‑Encoder (Retrieval / Re‑Ranking): A bi‑encoder embeds query and document separately for fast approximate search. A cross‑encoder scores a query–document pair jointly for higher precision; used as a re‑ranker.
- Knowledge Graph: A network of entities and relationships represented as nodes and edges. Useful for reasoning, constraints, and explainability.
- Graph Neural Network (GNN): A neural model that operates on graph structures, passing messages along edges to learn from connections as well as features.
- Reinforcement Learning (RL): Learning by acting and receiving rewards or penalties. Useful for control and sequential decision‑making; adapted to tune language models via preferences (RLHF).
- Policy / Value Function: In RL, the policy maps states to actions; the value function estimates expected reward from a state or state–action pair.
- Contextual Bandit: A simplified RL setting where each decision is a one‑shot choice with feedback, used for recommendations and pricing experiments.
- Self‑Supervised Learning: Learning from the structure within unlabeled data by predicting parts of the input from other parts (e.g., next token). The backbone of modern pretraining.
- Contrastive Learning: A method that brings similar pairs closer in embedding space and pushes dissimilar pairs apart. Central to many vision and text–image models.
- Curriculum Learning: Training that starts with easier examples and gradually increases difficulty, improving stability and speed.
- Knowledge Distillation: Training a smaller “student” model to mimic a larger “teacher,” preserving most performance with reduced size and cost.
- Quantization: Representing weights and activations with fewer bits (e.g., 8‑bit or 4‑bit) to reduce memory and increase speed, with careful calibration to limit accuracy loss.
- Pruning: Removing weights or neurons that contribute little, shrinking models with minimal quality loss.
- Adapters / LoRA / PEFT: Parameter‑efficient fine‑tuning methods that add small trainable modules or rank‑decomposed updates to a frozen base model, enabling task customization with modest compute.
- Prompt Tuning (Soft Prompts): Training virtual tokens (not visible words) that steer a frozen model toward a task or brand voice without updating all weights.
- Token Merging / KV Compression: Techniques that reduce the number of active tokens or compress attention memories to speed up inference in long contexts.
- Decoding Strategies (Greedy, Beam, Top‑k, Top‑p, Temperature): Rules for picking the next token when generating text. Greedy chooses the most likely token; beam keeps multiple partial candidates; top‑k and top‑p sample from the most likely subset; temperature adjusts randomness.
- Speculative Decoding: A small draft model proposes several tokens; a larger model quickly veri
21.3 Infrastructure and Operations
- CPU / GPU / TPU / Accelerator.: Processors used for AI workloads. CPUs handle control and general tasks. GPUs and TPUs are accelerators optimized for linear algebra, delivering much higher throughput for training and inference.
- High‑Bandwidth Memory (HBM): Memory bonded close to the processor with very high bandwidth. Essential for feeding data to large models quickly during training and inference.
- Interconnect (PCIe, NVLink, InfiniBand): The data highways between chips and servers. Faster interconnects allow parallel training and serving with less communication bottleneck.
- Throughput vs. Latency: Throughput is how much work a system completes per second (tokens/sec, requests/sec). Latency is how long a single request takes end‑to‑end. Batching raises throughput; it can raise tail latency if not tuned.
- Batch Size / Micro‑Batch: How many examples are processed together during training or how many tokens are grouped in serving. Micro‑batches break large batches into sizes that fit memory while preserving throughput via accumulation.
- Gradient Accumulation: During training, accumulating gradients over several micro‑batches before updating weights to simulate larger batch sizes under memory limits.
- Parallelism (Data, Tensor/Model, Pipeline): Data parallelism replicates the model across devices and splits the data; tensor/model parallelism splits the model across devices; pipeline parallelism splits layers into stages that process different mini‑batches concurrently.
- Optimizer State / ZeRO / Sharding: Optimizer state (e.g., momentum) consumes memory during training. Techniques like ZeRO shard model states and gradients across devices to train bigger models efficiently.
- Checkpointing: Saving model state periodically during training so you can resume after failures or roll back if quality regresses.
- Fault Tolerance: Designing jobs and services to continue or recover gracefully when nodes fail—critical for long training runs and 24/7 serving.
- Kubernetes / Orchestrator: Software that schedules and manages containers across servers. Used to deploy training jobs and inference services reliably.
- Model Serving: The stack that loads a model, accepts requests, runs inference, and returns results. Includes autoscaling, request routing, and safety filters.
- Autoscaling: Automatically adding or removing serving capacity based on load to control cost and maintain SLOs.
- KV Cache: In transformer decoders, the stored key–value pairs from previous tokens. Reusing them avoids recomputing attention over the entire history, speeding generation.
- Streaming: Sending partial outputs as they are generated to reduce perceived latency for users.
- Response Caching: Storing answers for repeated prompts or for deterministic tasks to avoid recomputation.
- Vector Database: A storage and search engine for embeddings. Supports approximate nearest‑neighbor search to retrieve semantically similar items quickly.
- Index (HNSW, IVF, PQ): Data structures that speed vector search. HNSW builds a navigable graph; IVF partitions space; PQ compresses vectors to save memory. Many systems combine these.
- Chunking: Splitting documents into retrieval‑friendly pieces—small enough to be relevant, large enough to preserve context. Often paired with metadata and hierarchical summaries.
- Metadata: Structured fields attached to chunks (source, author, date, permissions, topic). Improves filtering, ranking, and auditability.
- Freshness / Re‑indexing: Keeping the retrieval corpus up to date with source systems. Requires pipelines that detect changes, deduplicate, and rebuild indices safely.
- Access Control (RBAC, ABAC): Restricting who can see what. Role‑based access control uses roles; attribute‑based uses properties (region, project, sensitivity). Must be enforced in retrieval and logs as well as source systems.
- Secrets Management: Storing and rotating credentials (API keys, passwords, tokens) securely. Tools integrate with serving to inject secrets at runtime without exposing them in prompts.
- Observability: Seeing how systems behave in production—metrics, logs, and traces. Essential for debugging, performance tuning, and safety oversight.
- Tracing: A structured record of what happened for a request: prompt, retrieved context, model version, tools called, outputs, and times. Vital for audits and incident response.
- Latency Percentiles (p50/p95/p99): The time under which 50%, 95%, or 99% of requests complete. Tail latency (p99) often governs perceived performance.
- SLO / SLI / SLA: Service‑level objective (target), indicator (measurement), and agreement (contract). For AI: availability, latency, accuracy/groundedness, and safety incident rates.
- Canary / Blue‑Green Deployments: Releasing changes to a small slice (canary) or maintaining two production environments (blue/green) to enable rapid rollback if problems appear.
- Rollback / Kill Switch: Immediate reversion to a prior model/prompt/index or hard stop for a route or tool when incidents occur.
- Cost Management (FinOps for AI): Measuring and optimizing tokens per request, tokens per outcome, model routing, caching, and hardware utilization to control spend.
- Energy / PUE: Electricity use and Power Usage Effectiveness (ratio of total facility energy to IT energy). Important for sustainability and capacity planning.
- Edge vs. Cloud vs. On‑Prem: Edge runs models near where data is created (devices, stores, factories). Cloud runs in hyperscale data centers. On‑prem runs in your facilities or private cloud. Trade‑offs involve latency, privacy, cost, and control.
- Sovereign Cloud / Data Residency: Cloud offerings and deployment patterns that keep data and operations within specified jurisdictions and under specified operator controls.
21.4 Safety, Risk, and Compliance
- Content Policy: The written rules that say what the system should produce or refuse (e.g., no personal medical advice; no disallowed content). Policies translate law and company values into operational guidance.
- Moderation: Screening inputs and outputs for policy violations. Combines machine classifiers with rules and, for edge cases, human review.
- Safety Filter / Classifier: A model or rule that detects categories like hate speech, self‑harm content, sexual content, or violent threats. Good filters report confidence and support tuning for false positives vs. false negatives.
- Jailbreak: A prompt designed to make a model ignore instructions or content policy. Variants include role‑play prompts, obfuscated text, and translation tricks
- Prompt Injection (Direct / Indirect): Direct injection tries to override instructions in the user prompt. Indirect injection hides instructions in documents or web pages the system retrieves, causing the model to follow the attacker’s text rather than the system’s rules.
- Guardrails: Design features that reduce risk: grounding with citations, schema‑constrained outputs, tool allow‑lists, strict argument validation, permission checks, and abstention on uncertainty.
- Human‑in‑the‑Loop (HITL): A design that requires human review or approval before a system’s output or action is accepted. Necessary where stakes are high or validation is imperfect.
- Abstention / Refusal: A model choosing not to answer or act when it lacks information, confidence, permission, or policy clearance. A healthy behavior, not a failure, when conditions warrant.
- Safety Incident: An event where the system violates policy, causes harm, breaches privacy, misuses a tool, or substantially degrades performance. Incidents trigger containment, notification, and post‑mortem analysis.
- Risk Tiering: Classifying use cases by potential harm and regulatory exposure (e.g., low, medium, high risk). Higher tiers require stronger evaluation, oversight, and evidence.
- Model Card: Documentation for a model: intended uses, limitations, training and evaluation summaries, performance (including by subgroup), and update history.
- System Card: Documentation for a complete system (model + retrieval + tools + policies): design, data sources, evaluation, safety posture, and operations plan.
- Datasheet (for Datasets): Provenance, composition, collection methods, licenses, and known issues for a dataset. Supports lawful, safe use and auditing.
- Post‑Market Monitoring: Ongoing measurement after deployment to detect drift, incidents, and new risks. Includes telemetry, sampling for human review, and scheduled evaluations.
- Differential Privacy (DP): A technique that adds controlled noise so that results do not reveal whether any individual’s data was used. Strong for aggregates; can be used during training to reduce memorization of personal data.
- Federated Learning (FL): Training that keeps data on devices or in silos and aggregates model updates centrally. Reduces the need to move raw data; brings new security and robustness challenges.
- De‑Identification / Pseudonymization: Removing or masking direct identifiers. Helpful but not absolute; linkage attacks can sometimes re‑identify. Treat as risk reduction, not a guarantee.
- Data Minimization: Collecting and retaining only what is needed for a defined purpose. Reduces exposure and compliance burden.
- Consent / Lawful Basis: The legal ground for processing personal data (consent, contract, legitimate interest, etc.), which varies by jurisdiction and use.
- Data Lineage: Traceability of where data came from, how it was transformed, and where it went. Essential for audits, deletions, and debugging.
- Audit Log: An immutable record of actions and decisions—who accessed what, which model or tool acted, what inputs were used, and what outputs were produced.
- Explainability / Interpretability: Making a system’s behavior understandable. In practice: features used, rationale with citations, decision traces, or simplified surrogate models, depending on the audience.
- Transparency: Clear communication about how systems work, where data comes from, what limitations exist, and how to appeal or correct errors.
- Fairness / Bias: Measuring and mitigating performance differences across groups (e.g., geography, language, protected classes where applicable). Methods include balanced datasets, constraints during training, and post‑processing adjustments.
- Equalized Odds / Demographic Parity: Fairness criteria. Equalized odds seeks similar error rates across groups. Demographic parity seeks similar positive decision rates; may be inappropriate where base rates differ.
- Accessibility: Designing systems that work for people with disabilities (screen‑reader friendly outputs, captioning, clear language). Often a legal requirement and always good practice.
- Governance (Three Lines of Defense): A structure where delivery teams own controls (first line), independent risk/compliance reviews (second line), and internal audit verifies effectiveness (third line).
- Vendor Risk Management: Due diligence for providers who process your data or run core parts of your stack. Covers security, privacy, training rights, portability, and incident response obligations.
- Export Controls: Government rules limiting the transfer of certain chips, tools, or models across borders. Relevant when selling or deploying in restricted jurisdictions.
- Intellectual Property (IP) / Copyright: Rights around training data, retrieval corpora, and outputs. Requires licenses where needed, respect for terms of use, and processes for takedown and attribution.
- Data Subject Rights (DSAR): Rights to access, correct, or delete personal data. Your workflows must propagate deletions to indices, caches, and logs—not just primary stores.
- Retention Policy: Rules that define how long data, logs, and embeddings are kept and how they are disposed. Tied to legal and business requirements.
21.5 Metrics and Evaluation
- Offline vs. Online Evaluation: Offline measures quality on curated datasets without user impact. Online tests measure business outcomes and user experience in production (A/B tests). Both are necessary.
- A/B Test: A randomized experiment comparing two experiences (control vs. treatment). For AI, typical outcomes include resolution rate, quality scores, latency, and cost—with guardrails for safety.
- Power Analysis: A pre‑experiment calculation that estimates how large a sample is needed to detect a meaningful effect reliably.
- Golden Set: A small, carefully vetted set of examples that represent typical cases. Used for quick regression checks.
- Challenge Set / Hard‑Case Set: A set of difficult, diverse, or adversarial examples used to probe limits and prevent superficial progress.
- Confusion Matrix: Counts of true/false positives/negatives for classification. The basis for precision, recall, and many fairness measures.
- Precision / Recall / F1 :Precision is “of the items we predicted as positive, how many were correct?” Recall is “of the truly positive items, how many did we find?” F1 is their harmonic mean. Use when misses and false alarms have different costs.
- ROC‑AUC / PR‑AUC: Summary scores for classifiers across thresholds. PR‑AUC is more informative when positives are rare.
- Perplexity: A measure of how well a language model predicts tokens. Lower is better. Good for pretraining diagnostics; not a direct measure of usefulness or truthfulness.
- BLEU / ROUGE / METEOR / COMET: Text overlap and learned metrics for translation and summarization quality. Useful but imperfect; pair with human review and task‑specific checks.
- Exact Match / QA‑F1: Metrics for question‑answering: exact string match or token‑level F1 against reference answers.
- Pass@k (Code): Probability that a correct solution exists among k generated attempts. Used in coding benchmarks; sensitive to sampling strategy.
- Groundedness / Faithfulness (RAG): Whether generated claims are supported by retrieved sources. Measured by citation presence and entailment checks (does the cited text actually support the claim?).
- Hallucination Rate: Share of outputs containing unsupported or contradictory claims. Should be measured with references, not by surface fluency.
- Toxicity Rate / Safety Violations: Frequency of outputs that violate content policy categories (e.g., hate speech, self‑harm). Track false negatives as well as blocks.
- Jailbreak Success Rate: Share of adversarial prompts that cause policy‑breaking behavior. A core safety metric for agentic systems.
- Calibration / Brier Score / Expected Calibration Error (ECE): Calibration measures how well predicted probabilities match reality. Useful when the system must estimate its own confidence.
- Selective Risk / Coverage: Quality when the system is allowed to abstain. Reports performance on attempted cases and the share of cases handled, revealing the trade‑off between helpfulness and caution.
- Human Adoption / Acceptance Rate: How often users accept the model’s suggestion vs. editing or discarding it. A practical proxy for usefulness.
- Edit Distance: How much a human changed a draft (e.g., number of characters or tokens). Useful in assistive scenarios.
- Time‑to‑Resolution / Average Handle Time (AHT): Operational outcomes for service tasks. Must be paired with quality metrics to avoid perverse incentives.
- Latency (p50/p95/p99): Median and tail times from request to response. Tail latency drives perception and SLOs.
- Throughput (Tokens/sec, Requests/sec): Volume handled per unit time. Important for capacity planning.
- Cost per Outcome / Tokens per Outcome: Economics‑aligned metrics. Better than raw tokens per request because they reflect useful work, not just compute consumed.
- Energy per Token / per Outcome: An efficiency measure linking performance to environmental footprint. Useful for sustainability reporting.
- Cache Hit Rate: Share of requests served from retrieval or response caches. High hit rates reduce cost and latency.
- Retrieval Metrics (Recall@k, Precision@k, MRR, nDCG, MAP): Measures of how well a search system surfaces relevant documents. Recall@k asks “is at least one relevant document in the top k?” nDCG and MAP account for ranking quality.
- Re‑Ranking Gain: The improvement from applying a cross‑encoder re‑ranker after approximate search. Indicates how well the two‑stage retrieval pipeline works.
- Diversity / Novelty (Recommendations): Measures that discourage showing narrow or repetitive options. Track alongside click‑through and conversion.
- Safety False Positives / False Negatives: Over‑blocking vs. under‑blocking in moderation. Tuning requires monitoring both; false negatives usually carry higher risk.
- Drift Metrics (Population Stability Index, KL/JS Divergence): Statistics that detect shifts in input distributions or embedding spaces over time.
- Fairness Metrics (by Group): Performance and error rates broken out by language, region, device, or protected attributes where appropriate. Look for gaps and track mitigation progress.
- Human Rating (Likert, Pairwise Preference): Structured human judgments on quality, tone, or usefulness. Pairwise comparisons are often more reliable than 1–5 scales.
- Inter‑Rater Agreement (Cohen’s κ, Krippendorff’s α): Measures of how consistently human raters agree. Low agreement signals ambiguous tasks or unclear rubrics.
- Operational Uptime / Availability: Share of time the service meets its SLOs. Includes planned and unplanned downtime.
- Post‑Incident Time‑to‑Contain / Time‑to‑Recover: How quickly the team can stop harmful behavior and return to a safe state after an incident. A measure of operational maturity.