Skip to content

Concepts

The 60-second picture of how Expecto fits together. Every role benefits from reading this once, even if you only intend to use a fraction of the platform.

The core flow

Organization
  └── Project              ─ what we are receiving and for whom
        ├── Entity         ─ the target schema rows must conform to
        ├── DataContract   ─ the format a supplier agrees to deliver
        │     └── Revision ─ an immutable snapshot of that format
        ├── Transformer    ─ how contract source maps onto entity target
        └── Session        ─ one delivery: files → validated output

A Project groups everything needed to receive data for one use case. Inside it, an Entity declares the target schema (and row-level validation rules). A DataContract declares what a particular supplier promises to send, including the file types and column names. A Transformer is the pure mapping bridge between a contract and an entity. A Session is one delivery act — one supplier, one period, one set of files, walked through the pipeline.

Where each concept lives in detail

Concept Page
Organizations & multi-tenancy Organizations & multi-tenancy
Project & Entity Project & Entity
DataContract & Revisions DataContract & Revisions
Transformer Transformer
Catalog (reference data) Catalog
Business Rules Business Rules
Session lifecycle (FSM) Session lifecycle
Data Provider model Data Provider model
Glossary Glossary

How concepts relate to roles

  • A supplier primarily encounters Sessions and the validation errors that come out of them.
  • A project owner spends most of their time defining Entities, DataContracts, and Transformers.
  • An org admin works at the level of Organization, Data Providers, and access.
  • A developer interacts with the same concepts via API, plus the MCP tool catalogue.