- • Events move left to right through source, ingest, process, store, and consume stages
- • The hot path stays visually clear even with secondary batch flows
- • Labels name data assets instead of generic API verbs
- • Consent and PII paths are styled as security flows
- • PII lands in a restricted vault, separate from the analytics warehouse
- • Restricted joins are visible without implying default access
- • Dashboards read curated facts from the warehouse
- • Feature vectors are derived by batch from analytics tables
- • Consumption paths stay distinct from collection and consent handling