dbt models joined back onto their own parent

This rule flags a model that reads both a parent and that parent's own parent. It fires only when the middle model has no other child. A middle model that feeds several models is a shared concept, and passes.

The same rows reach the model by two paths, so it has to reconcile them, often with a distinct nobody can explain later. The middle model exists only to be rejoined, so two steps do the work of one.

Remove joins back onto a model's own descendant. Collapse the two steps into one model, or read the middle model alone and have it carry the columns you need.

Before:

-- int_order_totals reads stg_shop__orders, and nothing else reads it
select o.*, t.order_total
from {{ ref('stg_shop__orders') }} as o
join {{ ref('int_order_totals') }} as t using (order_id)

After:

-- int_order_totals now carries the order columns too
select *
from {{ ref('int_order_totals') }}

A middle model kept separate because it is expensive, or tested on its own grain, can be worth the extra step. We rate this rule low severity at medium confidence for that reason. Describe the reason on the middle model.

manifest.json alone. It does not need a layered project.

dbt_project_evaluator, rule fct_rejoining_of_upstream_concepts. Ours checks the same condition and threshold. Keeps the published one-child condition: the rule fires only where the intermediate model feeds nothing but the rejoining model. Without it every shared intermediate in a well-built DAG would be reported.

This means our check corresponds to their rule. It does not mean the publisher reviewed or endorses it.