Skip to content

AI & LLM Glossary: 60+ Essential Terms, Mechanisms & Architecture

Core Concept LearningAugust 15, 20268 min read

Artificial intelligence terminology moves so fast that concept definitions quickly become bloated with marketing fluff and overlapping jargon. Understanding the underlying mechanisms—how Transformers process tokens, how RAG retrieves vectors, how agents execute tools via MCP, and how LoRA fine-tunes models—is essential for engineering reliable production systems.

This guide establishes a working vocabulary of 60+ core AI terms grouped logically across 6 domain pillars. Each section includes technical definitions, engineering comparison matrices, architecture diagrams, and a clear-eyed evaluation of industry buzzwords. For orchestration patterns, see our Agentic Engineering Masterclass.

1. Model Architecture & Training Mechanics

Modern AI systems rest on fundamental architectural abstractions. At the core is Artificial Intelligence (AI)—technology enabling computers to perform tasks requiring human intelligence. Machine Learning (ML) enables systems to learn patterns from data rather than following static hardcoded rules. Deep Learning uses multi-layer neural networks for complex processing, while Generative AI creates new content across text, code, audio, and video.

The Transformer & Model Scaling

  • LLM (Large Language Model): General-purpose foundation models (e.g. GPT-4, Claude 3.5, Llama 3) pre-trained on massive text datasets.
  • SLM (Small Language Model): Compact, high-speed models (e.g. Phi-3, Gemma 2B) optimized for edge execution and low-latency task completion.
  • Transformer: The foundational neural network architecture utilizing self-attention mechanisms to process tokens in parallel.
  • Parameters: The learned numerical weights of a neural network, serving as a rough proxy for model capacity and hardware requirements.
  • Scaling Laws: Empirical observations showing model performance predictably improves as compute, dataset size, and parameter count scale exponentially.
  • Frontier Model: The state-of-the-art models representing the boundary of intelligence and capability at any given moment.
Model Architecture & Training Terminology
TermTechnical DefinitionEngineering ImpactKey Trade-off
TransformerSelf-attention neural network architectureEnables parallel token processing over long contextHigh VRAM quadratic memory complexity
ParametersLearned weight matrices in neural net layersDetermines memory footprint and reasoning depthLarger counts require higher inference VRAM
Pre-trainingSelf-supervised training on raw web corpusImbues base language & world knowledgeExtremely high compute cost ($1M–$100M)
Post-trainingSupervised fine-tuning & preference alignmentShapes raw next-token generator into safe assistantRisk of catastrophic forgetting
MoE (Mixture of Experts)Subnetwork routing per token executionScales total parameters while keeping inference cheapComplex distributed weight orchestration

Quick reference

  • Pre-training learns world facts via self-supervised next-token prediction; post-training aligns model behavior.
  • MoE architectures (e.g., DeepSeek-V3, Mixtral) activate only a fraction of expert parameters per token, lowering active inference compute.
  • LoRA and PEFT methods freeze base model parameters and train small rank-decomposition adapter matrices.

Remember this

Understand the progression from raw Transformers and pre-trained LLMs to post-trained, parameter-efficiently adapted models.

2. Inference, Runtime & Context Engineering

Executing a trained model is called Inference. Modern inference engines optimize response latency, time-to-first-token (TTFT), and throughput.

Tokens, Context Windows & Reasoning Runtimes

  • Token: The atomic unit of text processed by an LLM (~4 characters or 0.75 words in English).
  • Context Window: The maximum token length an LLM can evaluate in a single request (now regularly 128K to 1M+ tokens).
  • Reasoning / Thinking Models: Models that execute internal chain-of-thought tokens prior to outputting a final answer (e.g. OpenAI o3, DeepSeek R1).
  • Test-Time Compute: Allocating extra inference compute to allow a model to 'think longer' on complex logic problems.
  • Effort Levels: User-configurable dials controlling the depth of test-time compute thinking tokens.
  • Temperature: Randomness hyperparameter governing token selection probability (0.0 = deterministic; 0.7+ = creative).
  • Context Engineering: The discipline of curating context window payload structures, replacing static 'prompt engineering'.
Inference & Prompting Execution Terms
TermMechanismOptimal Use CasePitfall
TokensSub-word numerical encodingMeasuring API cost and context limitsTokenizer variations across languages
Context WindowRAM payload capacity for single callIngesting full repositories or documentsNeedle-in-a-haystack retrieval degradation
Test-Time ComputeDynamic inference-time search/thinkingComplex math, coding, and logical proofsIncreased end-to-end latency
System PromptHigh-level behavior framing directiveSetting persona, rules, and output schemasCan be hijacked via prompt injection
Zero-Shot / Few-ShotProviding 0 vs. N in-context examplesGuiding formatting and formatting consistencyFew-shot consumes context window tokens

Quick reference

  • Streaming delivers tokens to the user interface as they are generated rather than waiting for completion.
  • Latency / TTFT (Time to First Token) measures the responsiveness of streaming inference endpoints.
  • Chain of thought (CoT) forces models to output intermediate reasoning steps before declaring conclusions.

Remember this

Master tokens, context windows, and test-time compute to optimize inference speed, cost, and output accuracy.

3. Agents, Tooling & Model Context Protocol (MCP)

An AI Agent is an autonomous system designed to act toward goals rather than merely responding to single prompts. Agents break goals into plans, call tools, inspect results, and self-correct in execution loops. For container boundaries, see our Claude Code Sandboxing Guide.

Tool Calling, MCP & Swarm Topologies

  • Tool Calling / Function Calling: Enabling models to execute external APIs, SQL queries, or local code by emitting structured JSON schema parameters.
  • MCP (Model Context Protocol): The open standard created by Anthropic that standardizes how AI assistants connect to local/remote tools and data sources.
  • Connectors: Production MCP server plugins linking assistants to enterprise applications (Slack, Jira, GitHub, PostgreSQL).
  • Skills: Packaged workflow instructions teaching agents repeatable multi-step tasks.
  • Subagents: Specialized child agents spawned by a primary lead agent to execute parallel subtasks in isolated context scratchpads.
  • Sandbox: An isolated ephemeral container (e.g. Firecracker, Sprites, Docker) where an agent safely executes bash commands or code.
  • Human in the Loop (HITL): Required human confirmation gates before executing high-risk or irreversible operations.
Agentic Architecture & Tooling Matrix
ComponentFunctionStandard / ToolingKey Benefit
AgentGoal planning & tool execution loopClaude Code, LangGraph, AutoGenAutonomous multi-step problem solving
MCP ServerExposes standardized tools & resourcesModel Context Protocol (MCP)Universal interoperability across models
SubagentExecutes isolated subtask in child contextAgent tree / swarm topologiesPrevents context window clutter
SandboxHardware-isolated execution containerSprites.dev, MicroVMs, DockerPrevents accidental data loss or security breaches
HITL GateHuman approval before actionInteractive CLI / Web approval dialogsEnforces safety on write/delete operations

Quick reference

  • Agentic coding agents write, execute tests, inspect stack traces, and refactor code autonomously.
  • Reflection enables agents to evaluate their intermediate outputs against acceptance criteria before finalizing.
  • Computer Use / Browser Use enables agents to operate GUIs and web browsers via visual click/type actions.

Remember this

Build agentic systems using MCP tools, isolated sandboxes, and human-in-the-loop controls for safe automation.

4. RAG, Vector Search & Knowledge Systems

Retrieval-Augmented Generation (RAG) grounds LLMs by fetching relevant documents from external knowledge repositories prior to answer generation. This eliminates stale static cutoffs and eliminates hallucinations.

The RAG Data Pipeline

  • Chunking: Splitting raw documents into smaller text passages prior to embedding generation.
  • Chunk Overlap: Retaining a small overlapping text segment between adjacent chunks to prevent context fragmentation.
  • Embeddings: Dense numerical vector representations of text capturing semantic meaning in high-dimensional vector space.
  • Vector Database: Specialized databases (Pinecone, Qdrant, pgvector) optimized for nearest-neighbor similarity search.
  • Retriever: The engine fetching top-K candidate chunks using cosine similarity or Euclidean distance.
  • Reranking: Secondary scoring models (e.g., Cohere Rerank) that re-order candidate chunks by precise relevance to the prompt.
  • Hybrid Search: Combining keyword search (BM25) with vector similarity search for optimal recall and precision.
  • Graph RAG: RAG leveraging knowledge graph relationships across entities for multi-hop reasoning.
RAG Pipeline Stage Comparison
StageInputOutputPrimary Optimization Metric
ChunkingRaw Markdown / PDF document300–500 token text chunksContext preservation & semantic boundaries
EmbeddingText chunk string1536-dim vector arraySemantic representation quality
Vector SearchQuery embedding vectorTop-20 candidate chunksRecall @ K & search latency
RerankingQuery + Top-20 chunksTop-5 re-ordered chunksPrecision @ K & contextual relevance
GenerationSystem prompt + Top-5 chunksGrounded answer responseFaithfulness & zero hallucination

Quick reference

  • Metadata Filtering restricts vector queries by date, tenant ID, permission level, or department.
  • Agentic RAG gives the LLM full control over when to query, which search tools to use, and how to formulate sub-queries.
  • Grounding ensures every claim in the generated response references a specific retrieved document snippet.

Remember this

Construct RAG pipelines with chunk overlap, hybrid search, and reranking to achieve high precision and grounded factual answers.

5. Fine-Tuning, Quantization & Model Adaptation

Adapting general foundation models to specific enterprise domains requires targeted fine-tuning and quantization techniques.

PEFT, LoRA & Quantization

  • Fine-Tuning: Further training a pre-trained base model on domain-specific datasets.
  • Instruction Tuning: Fine-tuning a base model on instruction-response pairs to improve prompt following.
  • LoRA (Low-Rank Adaptation): A Parameter-Efficient Fine-Tuning (PEFT) technique that freezes base weights and trains low-rank adapter matrices.
  • QLoRA: Combining LoRA with 4-bit NormalFloat quantization to fine-tune 70B models on a single GPU.
  • Quantization: Converting high-precision floating point weights (FP16/BF16) to lower precision (INT8/INT4) to reduce VRAM requirements.
  • Distillation: Training a smaller 'student' model to emulate the output distribution of a larger 'teacher' model.
  • Synthetic Data: AI-generated training data used to train, evaluate, or align downstream models.
Model Adaptation Methods Matrix
MethodParameters UpdatedHardware RequirementBest For
Full Fine-Tuning100% of weightsMulti-GPU clusters (8x A100/H100)Domain adaptation with massive data
LoRA< 1% (adapter rank r)Single enterprise GPU (1x A10G/A100)Task-specific formatting & style
QLoRA< 1% (4-bit base model)Single consumer GPU (1x RTX 4090)Low-cost fine-tuning of 70B models
Quantization (GGUF/EXL2)0% (Post-training compression)CPU or low-tier GPUEdge inference & local desktop execution
Distillation100% of student modelStandard training GPUCreating fast, cheap domain-specific SLMs

Quick reference

  • Quantization from FP16 to INT4 reduces VRAM consumption by ~70% with minimal loss in benchmark accuracy.
  • Synthetic data generation allows frontier models to generate high-quality dataset pairs for training specialized SLMs.
  • LoRA adapter matrices allow dynamic hot-swapping of fine-tuned domain skills on top of a single shared base model.

Remember this

Use LoRA/QLoRA for low-cost fine-tuning and quantization for high-speed, cost-effective production deployment.

6. Alignment, Safety, LLMOps & The Hype Radar

Deploying AI in production demands resilient security controls, continuous evaluation, and a clear-eyed evaluation of market hype.

Alignment, Security & LLMOps

  • AI Alignment: Ensuring model outputs conform to intended human goals, ethics, and safety rules.
  • RLHF / RLAIF: Reinforcement Learning from Human (or AI) Feedback to optimize model response preferences.
  • DPO (Direct Preference Optimization): A streamlined preference optimization algorithm operating directly on preference pairs without a reward model.
  • Constitutional AI: Anthropic's method of training models against a written constitution of safety principles.
  • Prompt Injection: A security attack where untrusted user input overrides system prompt instructions.
  • Jailbreak: An adversarial attempt to bypass a model's safety and policy guardrails.
  • Guardrails / Safeguards: Real-time input/output filters (e.g. NeMo Guardrails) ensuring responses stay safe and compliant.
  • LLMOps: Processes and infrastructure for deploying, evaluating, tracing, and monitoring production LLM applications.
  • Evals / Benchmarks: Automated testing suites (SWE-bench, MMLU, GPQA) measuring model performance.
  • Model Drift: Degradation of model accuracy over time as real-world input distributions shift.

🚨 The Buzzword Hype Radar: What to View with Skepticism

1. 'AGI is Imminent': Marketing claims predicting Artificial General Intelligence within months often conflate benchmark optimization with true general reasoning. 2. 'Reasoning' Marketing Labels: Every new model update labeled 'reasoning' may simply be executing test-time compute tokens or basic chain-of-thought prompts. 3. 'Agentic' Applied to Simple Loops: Adding a single while loop around an API call does not constitute a full agentic architecture. 4. '10x Engineer Replacement': AI tools augment developer velocity, but autonomous systems still require human architectural direction, code review, and domain validation. 5. Unpublished Parameter Counts: Skepticism is warranted when vendor claims omit model parameter sizes, training token counts, or benchmark contamination checks.

AI Safety & LLMOps Perimeter
Security LayerThreat / RiskMitigation StrategyProduction Metric
Input FilterPrompt Injection & JailbreaksXML delimiter isolation & regex sanitizationInjection block rate
Preference AlignmentHarmful or toxic generationRLHF / DPO & Constitutional AISafety eval benchmark score
Output GuardrailHallucinations & PII leaksGrounding checks & PII masking filtersPII redaction rate
LLMOps ObservabilityHigh latency & budget overrunsSpan tracing (LangSmith/Phoenix) & cost alertsp95 Latency & cost per 1K reqs
Evals SuiteModel drift & regressionAutomated regression testing against gold datasetsPass rate on SWE-bench / custom evals

Quick reference

  • Benchmark Contamination occurs when evaluation test sets accidentally leak into model pre-training corpora.
  • Vibe Coding refers to building software primarily through natural language prompting rather than writing raw source code.
  • Open Weights models (Llama, DeepSeek) provide downloadable weights for self-hosted deployment.

Remember this

Combine aligned model checkpoints with automated Evals and LLMOps tracing, while maintaining a healthy skepticism toward vendor hype.

Key takeaway

Mastering the working vocabulary of AI, LLMs, and agentic systems is the key to building predictable, scalable software in 2026. By distinguishing between core architecture, retrieval mechanics, agentic tool loops, model adaptation, and security guardrails, engineers can cut through vendor marketing hype and deliver reliable AI systems.

Share:
PK

Polo Khan

Lead Author & Systems Architect

Software engineer and distributed systems architect specializing in backend scalability, cloud-native infrastructure, databases, and AI engineering workflows. Author and maintainer of Core Concept Learning.

Human-Engineered & Fact-CheckedOriginal Visual DiagramsEditorial Standards →Send Feedback

Related Articles

A search team upgrades their embedding model for better quality, re-embeds only newly added documents with it, and leave

Read

Jul 22, 2026 · 7 min read

A support document explaining refund policy, shipping policy, and warranty terms gets embedded as one 2,000-token chunk

Read

Ask ChatGPT a general-knowledge question and it answers from what it learned during training. Ask a support bot "what's

Read

Explore this topic

Keep learning

Follow a structured path or browse all courses to go deeper.