Source — a database Evalyst reaches through a native driver (Postgres, MySQL, Snowflake, BigQuery), attached to your workspace with read-only credentials. Not to be confused with a connector.

Connector — an agent-written module for an API or service that isn’t a SQL database. Validated in a sandbox. See connectors.

Semantic model — the versioned record of what your data means: metrics, exclusions, gotchas, join keys. Yours, not ours. See the semantic model.

Ground-truth question — a question with an answer a human confirmed. The unit the gate is built from.

Eval bank — the set of confirmed ground-truth questions for one source.

Silent error — an answer that is confident, plausible, and wrong, with nothing to signal it. The headline number in every run, and the one that must be zero.

Abstention — the agent declining to answer because the data can’t support a conclusion. Counted as a success, not a failure.

The gate — the rule that a change to a semantic model cannot go live unless the bank comes back with zero silent errors and at least 90% accuracy. See the eval gate.

Verified badge — the scorecard on a source: accuracy, silent-error count, bank size, last run. A measurement of that source’s own bank, not a claim about the product.

Read-only verified — the state of a source whose credentials were proven unable to write at attach time. A source where an admin accepted write-capable credentials instead keeps saying unverified, deliberately and permanently, until real reader credentials are supplied.

Widget — a saved chart or table pinned to a dashboard, backed by one of three things: a parameterized query against one source, a cross-source workflow, or a materialized rollup. Refreshing one re-runs that artifact with no model involved.

Workflow — a cross-source analysis: reduce at each source, then combine the small results in DuckDB. A workflow names as many extracts as the question needs, and an extract is either a query against an attached database or the rows a connector last pulled from an API — so one query can join two production databases and a billing API together.

Workspace — your organisation’s tenancy boundary. Every row carries it, and it is enforced both in the application and in the database.