Glossary

Amdahl's docs use about a dozen words in a specific sense. Each is defined here once. If a page uses one of these without explaining it, this is the page it means.

The data

Corpus — every customer conversation Amdahl holds for your workspace: call transcripts, meeting notes, and emails, normalized into one searchable shape. When a page says "your own corpus" it means this, not the open web.

Warehouse — the queryable, row-shaped view of that corpus. Search runs SQL against it; a conversation becomes rows you can filter, count, and group.

Interaction — the warehouse's unit of conversation: a grouped turn, not a whole call. Several things said in a row by one speaker collapse into one interaction row (they average 2.88 atomic utterances), so an interaction is smaller than a meeting and bigger than a sentence.

Grain — what one row of a result actually counts. A query at deal grain returns one row per deal; at interaction grain, one row per grouped turn. The same question at two grains gives two different, both-correct numbers — which is why a count is only meaningful once you know its grain.

Coverage — how much of your data a given answer could actually see. Reported on the response rather than assumed, so a thin answer says it is thin instead of looking like a confident zero.

Asking

Lane — which of the three search strategies ran: filter (typed predicates, deterministic, no model), fuzzy (plain language turned into SQL), or semantic (meaning-based similarity). One endpoint, three lanes; mode picks one or auto routes for you.

Chat — the async door. You hand over a question that needs real investigation, and Amdahl runs it server-side and returns handles you poll.

Master — the general-purpose agent that runs a Chat turn. It has access to the warehouse, customer-voice themes, the knowledge base, memory, and — when enabled — outside market search. A named agent from the library is a Master turn running that agent's prompt.

Agent — a saved, reusable prompt your workspace can dispatch by name. Not a separate engine: the same Master turn, specialized.

Routine — a cron that fires a fresh Chat on a schedule. A standing weekly sweep, a daily pipeline pulse.

Grading

Eval — a configured grading pipeline: the inputs it accepts, the cases it grades, and the graders that score each one. prompt-and-message-eval is the built-in one.

Run — one execution of an eval against one submission. Runs are immutable once finished, so a run id is a stable thing to cite.

Dimension — one axis a submission is graded on (relevance, specificity, evidence, and so on).

Rubric line — the judge's verdict on one dimension: a binary pass or fail with a sentence of reasoning behind it. One per dimension, which is why the score is a count of dimensions passed rather than an average of opinions — checks_passed / checks_total is that fraction.

Gate run — a run that grades only what you submitted and stops: no rewrite, no improved version, no suggestions. Cheaper and faster than the full loop, and the right mode when you only need a pass/fail before sending.

Tier — what a quote licenses you to claim. account backs "you told us"; segment backs "teams like yours"; corpus backs "the people we talk to say". Reaching past a quote's tier is graded as a grounding failure, not a style note.

Evidence pool — the quotes retrieved for a run, before the judge saw them. Bigger than the handful the report cites; the counts strip on a report opens it.

Lift — the improved side's score minus the submitted side's, where both halves come from the same judge call (before_paired). It is not the gap between the two dials on a report: those are graded under different conditions, which is why the server computes lift rather than leaving you to subtract. Read the caveat on Evals before building anything on it — lift mostly measures how low the submitted side scored, so the largest lifts come from the weakest drafts.

Wire shapes

Envelope — the data wrapper around every successful JSON response. The field you want is one level in: .data.results, not .results. Four responses are deliberately not enveloped — the .csv and .jsonl file downloads, event streams, and GET /openapi.json.

Handle — the id an async call returns immediately so you can poll or stream for the answer instead of holding a connection open.

Operation — one callable thing on the API, named resource.verb (search.query, evals.run). The tool catalog lists every one. Over MCP these are reached as an action on one of three tools — see Connect your agent.

See also

• Quickstart — these words in use, against your own data.
• Tool catalog — every operation, generated from the server.