Retrieval-Augmented Generation (RAG) #
Also known as RAG
Retrieval-Augmented Generation (RAG) retrieves relevant passages at query time and feeds them into an LLM's context.
Read the full entry →Plain-English definitions for the vocabulary behind our work: retrieval, agents, evals, cost. Each one links back to the insight, capability or tool that goes deeper.
Also known as RAG
Retrieval-Augmented Generation (RAG) retrieves relevant passages at query time and feeds them into an LLM's context.
Read the full entry →Also known as vector embeddings
Embeddings are numeric vectors that place similar content close together in vector space.
Read the full entry →The context window is the maximum text, measured in tokens, a model can consider at once.
Read the full entry →A token is the basic unit of text an LLM reads and writes.
Read the full entry →A model-agnostic architecture lets an application swap or route between LLM providers without a rewrite.
Read the full entry →Fine-tuning trains a model's weights on your own examples, changing its behavior directly.
Read the full entry →Also known as semantic search, similarity search
Vector search finds the nearest matches to a query by comparing embeddings, not exact keywords.
Read the full entry →Chunking splits source documents into smaller passages before embedding, so retrieval returns focused text.
Read the full entry →An agent is an LLM given a loop, memory, and tools it can call.
Read the full entry →Also known as function calling
Tool calling lets a model request a structured action instead of only generating text.
Read the full entry →Also known as MCP
MCP is an open standard for connecting LLM applications to tools and data sources.
Read the full entry →Context engineering decides what occupies a model's context window at every step, and in what order.
Read the full entry →A tool contract is the schema a tool exposes to a model.
Read the full entry →An idempotent operation produces the same result no matter how many times it runs.
Read the full entry →Structured output constrains a model's response to a defined schema instead of free-form prose.
Read the full entry →Guardrails are the checks that keep an LLM or agent inside acceptable bounds in production.
Read the full entry →A golden path is the single sanctioned way to do a common piece of work.
Read the full entry →An MCP gateway is a shared layer in front of several MCP servers, centralizing controls.
Read the full entry →Context rot is a model's declining ability to use context well as it fills with stale material.
Read the full entry →Compaction summarizes or drops older context to make room in a filling window.
Read the full entry →Context isolation gives each delegated unit of work its own scoped context window.
Read the full entry →Also known as evals, evaluation suite
An eval suite is a versioned set of test cases that measures whether outputs are good.
Read the full entry →LLM-as-judge uses another LLM to score a model's outputs against a rubric, at scale.
Read the full entry →Observability captures traces of every prompt, retrieval, tool call, and response for debugging.
Read the full entry →A hallucination is a confident, fluent output that is factually wrong or unsupported.
Read the full entry →Prompt injection is untrusted input crafted to override a model's system prompt or task.
Read the full entry →Also known as shadow testing, dark launch
A shadow deployment runs a candidate release against real production traffic, offline, before release.
Read the full entry →Inference cost is what it costs to run a trained model on a request.
Read the full entry →Notebook-to-production is the gap between a working prototype and a system that runs reliably.
Read the full entry →Also known as canary deployment, canary rollout
A canary release exposes a change to a small, deliberately chosen slice of traffic first.
Read the full entry →Also known as model drift, quality drift
Output drift is a gradual change in a live system's output, with no release behind it.
Read the full entry →Model deprecation is a provider retiring a model version on its own schedule.
Read the full entry →Acceptance rate is the share of an agent's proposed changes a human reviewer approves.
Read the full entry →Also known as DPA
A DPA is the contract naming a vendor as a processor of personal data.
Read the full entry →Data residency is where data is physically processed and stored, not where users are located.
Read the full entry →Red teaming is deliberately attacking your own AI system to find what breaks first.
Read the full entry →An AI register is a current list of every system that touches a model.
Read the full entry →A high-risk AI system is one classified as carrying enough decision impact to trigger heavier compliance.
Read the full entry →Human oversight is a checkpoint where a person can meaningfully approve, reject, or intervene.
Read the full entry →A system card is a short document stating an AI system's purpose, limits, and owner.
Read the full entry →Also known as shadow use
Shadow AI is a model or tool used without going through the sanctioned path.
Read the full entry →Tool poisoning hides an instruction in a tool's description that the model reads as legitimate.
Read the full entry →A confused deputy is a component tricked into using more authority than a request deserves.
Read the full entry →Source: https://customlabs.io/glossary/