Contract

• Input: source data descriptions, target schema, quality requirements.
• Output: pipeline architecture + quality rules + schema evolution.
• Side effects: may process data when executed (read-only or write to target).
• Dependencies: source access, target access.
• Stop condition: architecture saved; quality rules defined.
• Risk: medium — data corruption risks; requires testing.
• Boundary: defines pipeline; execution requires approval.

ETL Pipeline Design

Design an ETL / ELT pipeline — extraction, transformation, load — with reproducible steps, schema evolution, and data quality checks.

Process