Foundations¶
The Foundations section defines ETLantic's product identity, architectural boundaries, vocabulary, and documentation stability model.
Recommended Order¶
Start here (required):
- Documentation Status — how to read Available vs Future design
- Core Concepts
- Architecture
- Security Model
- Glossary
Optional philosophy (same thesis, different angles—skip on the first pass):
Foundation in One Sentence¶
ETLantic uses typed Python declarations and three portable contract standards to build a validated logical pipeline, resolves that pipeline into a deterministic
PipelinePlan, and delegates realization to external backends through plugins.
Non-Negotiable Boundaries¶
- ODCS, DTCS, and DPCS own contract semantics.
- ContractModel operationalizes data contracts.
- ETLantic owns typed authoring, validation, planning, and coordination.
- Plugins own backend adaptation.
- External systems perform computation, scheduling, and persistence.