drt docs my-drt-project
drt 0.7.10
Lineage

DAG — visual direction mock v2 (hand-positioned)

Ownership at a glance: what drt manages, what it reads, what it writes.

sync — drt-managed code data store external app lookup — sync reads a destination success partial failed 3 → DLQ dead-letter rows ⚠ drift schema drift (audit)
SOURCES external · read SYNCS managed by drt version-controlled YAML DESTINATIONS external · write lookup bq_prod BIGQUERY pg_replica POSTGRES users_to_pg incremental success products_to_pg full success orders_to_pg upsert partial 3 → DLQ alerts_to_slack incremental failed 12 → DLQ users_to_hubspot mirror success public.users POSTGRES public.products POSTGRES public.orders POSTGRES ⚠ drift #alerts SLACK contacts HUBSPOT

Drill-down — table & column level (concept)

Click a sync (or expand in place) to open its ego-graph at column grain. Column facts are declared in field_mappings / mask — no SQL parsing needed on the write side.

sales.orders BIGQUERY · TABLE from model SQL — planned (manifest schema v2) orders_to_pg partial FIELD_MAPPINGS order_id customer_id email mask amount … 4 more columns public.orders POSTGRES COLUMNS id customer_id email amount_usd
Visual-direction mock — hand-positioned SVG. The real thing is emitted by the layout engine (#677 follow-up); every node links to its detail page. DLQ counts arrive via manifest schema v2 (#698); drift badges need a persisted drift-audit artifact (storage TBD).