Glossary

The single definition point for Expecto terms. Each entry links to its full concept page where one exists.

Approval mode : A project setting controlling sign-off: auto, single approval, or dual approval. See Session lifecycle.

Catalog : Reference data (a dictionary) used in transforms and rules, stored as Parquet. See Catalog.

DataContract : A supplier's format agreement — typed sources with parsing config and expected schema. See DataContract & Revisions.

Data Provider : A supplier organization with scoped submission access. See Data Provider model.

Entity : The target schema your normalized data lands in, plus its row-level validation rules. See Project & Entity.

Health : Whether a session is blocked (e.g. by ERROR violations), as opposed to its pipeline stage. See Session lifecycle.

Organization : The tenant root; every object belongs to exactly one. See Organizations & multi-tenancy.

Project : The container for one intake use case — entities, contracts, transformers, rules, export, providers. See Project & Entity.

Reconciliation : Cross-entity checks on a project — keyed (FULL OUTER JOIN on a key) or global (CROSS JOIN of scalar aggregates). See Business Rules.

Revision : An immutable snapshot of a contract's format: draft → active → frozen. See DataContract & Revisions.

Session : One delivery act, run through the pipeline CREATED → … → EXPORTED. See Session lifecycle.

Source : One typed file role within a DataContract, with a Frictionless Table Schema. See DataContract & Revisions.

Transformer : The pure mapping bridge from a contract's sources to an entity's columns, via DuckDB expressions. See Transformer.

Validation rule : A row-level expression on an entity; failing rows become violations with a severity. See Business Rules.

Violation : A row (or check) that failed a rule, reported with severity ERROR / WARNING / INFO, or marked not_applicable. See Business Rules.