Architecture
Trust but verify at every boundary
Walk a Stripe charges export through ingest → stage → mart → egress with four linked contracts. Keep dbt, Great Expectations, and Soda for post-modeling tests — they check modeled logic; DataContractGate verifies payloads crossing edges. Click a gate for the contract name, a YAML excerpt, a concrete violation, the endpoint, and the GitHub file.
Sources
Stripe Charges API
Raw
Landing zone
Staging / marts
Modeled tables
Outbound
Reverse ETL / partners
LLM / agent
Structured JSON
App / tools
Only conforming JSON
Contract gate (click)
Data store / system
Post-modeling tests (keep them)
Stripe chain + write-up: examples/contract-chain/stripe · architecture doc · examples/dbt · examples/airflow