Data lineage diagram from source systems to BI dashboards

A horizontal data lineage diagram rendered in a clean, professional infographic style suitable for technical documentation. Landscape orientation, 2400x1400 pixels, flat-design vector aesthetic with subtle shadows and rounded rectangles. **Layout:** Six vertical columns arranged left to right, each column representing a layer of the data stack. A light gray background (#F8FAFC) spans the full diagram. Each column has a subtle header band in slate (#475569) with white text. **Column 1 — Source Systems (leftmost):** A stack of five rounded cards, each with a recognizable logo mark and a short label: - Stripe — "payments, subscriptions" - Salesforce — "accounts, opportunities" - PostgreSQL (application DB) — "users, orders, products" - Segment — "event stream" - Zendesk — "support tickets" **Column 2 — Ingestion:** Two rounded cards: - Fivetran — "batch, 15 min cadence" - Kafka Connect — "CDC + events" Small clock icons next to each indicate cadence. **Column 3 — Raw Layer:** A stack of small table icons labeled raw_stripe.subscriptions, raw_sfdc.accounts, raw_app.users, raw_segment.events, raw_zendesk.tickets. Each has a tiny "immutable" lock icon. Column header reads "RAW — untouched ingest". **Column 4 — Staging and Intermediate (two sub-rows):** Top sub-row labeled "stg_" with tables stg_subscriptions, stg_accounts, stg_users, stg_events, stg_tickets. Bottom sub-row labeled "int_" with int_customer_profile, int_revenue_daily, int_support_load. **Column 5 — Marts:** Three grouped boxes labeled by business domain: - marts_finance — fact_subscriptions, fact_invoices, mrr_daily - marts_product — fact_events, user_activity_daily - marts_support — ticket_summary Each group is color-coded: finance in emerald, product in indigo, support in amber. **Column 6 — Consumers (rightmost):** Three cards stacked vertically: - Mode Analytics — "Exec revenue dashboard" - Hex — "Product analytics notebooks" - ML Features API — "Churn model features" **Arrows:** Thin gray arrows (#94A3B8) connect every upstream dependency to its downstream consumer. Arrowheads are subtle and uniform. Lines route orthogonally with rounded corners, never crossing through nodes. **Highlighted lineage path (bright teal #14B8A6, 3px stroke, 100% opacity):** A single emphasized path traces: Stripe -> Fivetran -> raw_stripe.subscriptions -> stg_subscriptions -> int_revenue_daily -> marts_finance.fact_subscriptions -> Mode Analytics "Exec revenue dashboard". Every node and arrow on this path glows subtly; everything off the path drops to 40% opacity. A small label floats above the path: "Lineage: subscription revenue -> exec dashboard". **Legend (bottom-left corner):** Small key showing: - Dotted arrow = optional dependency - Solid gray arrow = standard dependency - Teal arrow = highlighted lineage - Lock icon = immutable layer - Clock icon = scheduled refresh **Footer strip (full width, dark slate):** Small white text: "Generated by the data catalog -- refreshed hourly -- owner: data-platform@company". **Typography:** Inter font throughout. Column headers 18pt bold white on slate. Node labels 11pt dark slate. Small annotations 9pt medium gray. Consistent padding inside every card. The overall feel should be calm, orderly, and trustworthy -- closer to a subway map than a marketing poster.