Working With Dbt Mesh

The core insight is simple: upstream data flows through ref(), not source(), and every cross-project reference needs an explicit project name. It walks through dependencies.yml first, shows you how to disambiguate models with identical names across projects, and covers the four governance primitives (contracts, groups, access modifiers, versions) in adoption order. One critical callout: cross-project refs require dbt Cloud Enterprise, and the skill correctly gates you before writing two-argument refs if you can't confirm the plan level. Useful if you're either setting up mesh from scratch or debugging why a ref() is ambiguous.