Glossary

Shared terminology for the platform, data-product model, orchestration layer, semantic layer, and operations guides.

API key

A credential presented in X-API-Key for authenticated API or CLI access.

A durable operational output with dependencies, checks, freshness, and materialization behavior.

A request to reprocess a selected historical slice of an asset.

The top-level container for schemas and related database objects.

A policy that rewrites or obfuscates a column value for selected principals or groups.

A governed package of outputs, semantic entrypoints, ownership, contract, and release metadata.

YAML documents that define desired platform state and are applied through validate-plan-apply workflows.

A business ownership boundary used to group data products and teams.

A privilege assignment on a securable object.

A collection of principals used to manage access in bulk.

The provenance graph that explains upstream, downstream, and column-level derivation relationships.

Reusable SQL logic that can be shared across models and projects.

A named semantic definition for a business-facing measurement.

A document of executable SQL cells that can be explored interactively and promoted into durable outputs.

A user or service identity recognized by the platform.

The published description of what a data product provides, who it serves, and how it should be used.

A policy that restricts which rows are visible during query execution.

A reusable business-facing model that defines metrics, dimensions, relationships, and optional pre-aggregations.

The end-to-end request path where authentication, grants, row filters, and column masks are applied before results are returned.

Cross-resource validation performed by the CLI after basic schema validation passes.

An ownership group responsible for building or supporting products within a domain.