Skip to main content

Plain-English field lexicon

The Decoder

12 terms · 3 clusters

Familiar analogy, precise definition, and a real example for the language behind agentic systems—without sanding off the technical meaning.

The Foundations

What the model is, underneath — before any talk of "agents".

  1. Analogy

    Sophisticated autocomplete — the same idea as your phone guessing the next word, trained on far more text and far better at it.

    Definition

    A "large language model": software that predicts the most likely next chunk of text from patterns it learned in training. It generates language; it does not look things up.

    In practice

    Ask it for a quote and it produces something that sounds right — because it is predicting plausible text, not retrieving a stored record.

  2. Token

    Analogy

    A chunk of text — roughly three-quarters of a word. The unit the model reads and bills in.

    Definition

    The fragments a model breaks text into. Around 100 tokens ≈ 75 English words. Limits and pricing are counted in tokens, not words or characters.

    In practice

    "strawberry" can be three tokens — which is part of why a model can miscount the letters in it.

  3. Context window

    Analogy

    The model's working memory — a desk. Pile on too many papers and the earliest ones slide off the edge.

    Definition

    Everything the model can see at once: your prompt, the conversation so far, attached files, and its own reply. Past the limit, earlier content is dropped — and nothing persists once the session ends.

    In practice

    In a long chat it "forgets" what you said at the start — that text fell off the desk.

  4. Prompt

    Analogy

    The brief. Closer to writing instructions for a new contractor than to programming.

    Definition

    The text you give the model — question, instructions, context. Its quality shapes the quality of the output.

    In practice

    "Summarise this" versus "Summarise this in three bullets for a CFO" pull sharply different results from the same model.

How Agents Act

What turns a chatbot that answers into something that does things.

  1. Analogy

    A worker you delegate to: brief it, and it takes steps on its own. A chatbot answers; an agent acts.

    Definition

    An LLM that runs tools in a loop toward a goal — it acts, checks the result, decides the next step, and repeats until done.

    In practice

    "Fix the failing test": it reads the test, edits the code, re-runs the suite, and stops once it passes.

  2. Agentic

    Analogy

    The adjective for "acts like an agent" — multi-step and self-directed, not one question and one answer.

    Definition

    Describes AI that plans and takes a sequence of actions with some autonomy, adapting as new information comes back.

    In practice

    An "agentic workflow" books the whole trip end to end; a chatbot only tells you how to book it.

  3. Tool use

    Analogy

    Letting the model pick up the phone. On its own it can only write text; a tool lets it do something in the real world.

    Definition

    Also called "function calling": the model requests an action from outside software — search the web, read a file, hit an API — and the result comes back into its context.

    In practice

    Asked for today's weather, it calls a weather tool instead of guessing.

  4. Analogy

    USB-C for AI — one standard plug so any agent can connect to any data source or tool.

    Definition

    The Model Context Protocol: an open standard (Anthropic, 2024) for connecting AI systems to external tools and data without building a custom integration for each one.

    In practice

    An MCP server for your docs lets an agent read them without bespoke glue code.

Building & Trusting It

The scaffolding, the guardrails, and why it sometimes makes things up.

  1. Analogy

    The cockpit around the engine. The model is the engine; the harness is everything that makes it useful and safe to fly.

    Definition

    The runtime around the model — the loop, tool access, memory, prompts, and guardrails. The model reasons; the harness does everything else.

    In practice

    Two products built on the same model can behave nothing alike because their harnesses differ.

  2. Analogy

    Letting it check the notes before answering, instead of going from memory.

    Definition

    Retrieval-Augmented Generation: fetch relevant documents at question time and have the model answer from them. It reduces made-up answers — it does not eliminate them.

    In practice

    A support bot that quotes your actual help docs rather than inventing a policy.

  3. Human-in-the-loop

    Analogy

    A dial, not a switch — from "asks before every move" to "acts and reports back".

    Definition

    How much the agent does without you: in-the-loop (you approve each action), on-the-loop (it acts, you monitor), or out-of-the-loop (fully autonomous).

    In practice

    An agent that asks before deleting files is in-the-loop; one that opens a pull request for your review is on-the-loop.

  4. Hallucination

    Analogy

    A confident bluff. It is generating plausible text, so "I don't know" rarely comes naturally.

    Definition

    When a model states something false as if it were true — because it predicts likely text rather than retrieving verified facts.

    In practice

    It cites a court case that does not exist: fluent, well-formatted, and entirely invented.