AIVAX

Practical guides and case studies

Glossary and cheat sheet

Look up essential agent vocabulary and use a compact checklist for prompts, knowledge, tools, safety, and cost.

  • Unit 5 of 6
  • 12 min
  • Beginner

In this unit, you will learn

  • Explain common agent terms in everyday language.
  • Distinguish model behaviour from application responsibilities.
  • Find the Learn unit that develops a concept in depth.
  • Apply practical checks before changing an agent.

You do not need to memorise every technical term before building a useful assistant. You do need a shared vocabulary when discussing what it may know, what it may do, and who checks its work. Use this page like a workshop reference card: find the unfamiliar word, then follow its link when the distinction affects your design.

The terms below describe general concepts, not guarantees about a particular product. “Structured” does not mean “true”, “authenticated” does not mean “allowed to do everything”, and “automated” does not mean “unaccountable”. These distinctions matter more than remembering the abbreviations.

Glossary #

The tabs group terms alphabetically. Each entry gives a short meaning and points to a lesson that explains its practical use.

A/B test — A comparison that assigns comparable users or cases to different versions so their outcomes can be evaluated fairly; see A/B testing.

Agent — Software that combines a model with instructions, context, and permitted tools to pursue a bounded task; see Introduction to AI agents.

API — An application programming interface is a defined way for one program to request information or actions from another; see Connecting to existing systems.

Authentication — A process that checks who a user or system is, rather than deciding every action they may perform; see Authentication and permissions.

Authorisation — The decision about which information or actions an identified user may access in a particular situation; see Authentication and permissions.

Bias — A systematic tendency that can produce unfair or unrepresentative outcomes rather than random mistakes; see Bias, fairness, and responsible AI.

Cache — Stored information or a previous result reused to avoid repeated work, subject to freshness and access restrictions; see Cost optimisation and caching.

Channel — The place where people interact with an assistant, such as a website chat or messaging service; see Integrating channels.

Chunk — A smaller passage made from a larger document so relevant information can be retrieved without sending everything; see Preparing documents for knowledge.

Citation — A reference that lets the reader inspect the source supporting an answer’s particular claim; see Writing good documents.

Context — The instructions, messages, facts, and tool results supplied to the model for its current response; see Adding context.

Context window — The model’s capacity for the tokens considered within a request, with accounting details depending on the model; see Context window, tokens, and cost.

The working cheat sheet #

These rules fit on a project review agenda. They are questions to verify, not magic phrases to paste into every prompt. Apply them to the actual sources, systems, and people involved.

Prompts: specify the job

State the goal, relevant context, output format, and limits. Include an example when the format is hard to describe. Remove contradictory rules. Tell the assistant what to do when information is missing.

Knowledge: maintain the evidence

Use approved, current documents with owners and clear scope. Keep exceptions next to their rules. Test whether the relevant passage is actually retrieved before changing the wording of the model’s answer.

Tools: keep permissions narrow

Give each operation a clear purpose and validate inputs outside the model. Distinguish reading from writing. Confirm consequential changes, prevent duplicate actions, and verify the result before claiming success.

Safety: provide a real exit

Collect only necessary data, enforce access before retrieval, and treat external content as untrusted. Explain that the assistant is automated. Make the route to a person visible and operational.

Cost: measure useful outcomes

Track the whole task, including search, tools, retries, review, and rework. Reduce unnecessary context before sacrificing evidence. Compare cost per successfully resolved issue rather than cost per message alone.

Resolve common confusions #

Does adding knowledge train the model?

Usually not. Retrieval places selected documents into the current request, much like putting reference pages on a desk. Training changes the model itself. Updating a searchable document and retraining a model are different operations with different costs and controls.

Does a tool call mean the task succeeded?

No. The model may request an operation, but software must validate and execute it. The operation can fail or have an uncertain result. Success should be reported only after the system confirms the intended outcome.

Does a citation make an answer correct?

No. The source might be outdated, outside the user’s scope, or unrelated to the claim. Check both the source’s authority and whether its actual text supports the answer. A credible-looking link is not evidence by itself.

What’s next: choose a route through the material with FAQ and learning paths by profile.

Knowledge check

Which term describes deciding whether an identified employee may access a restricted policy?

Type to search the documentation.