Dagster finds dependencies in two ways.
A parameter named after an upstream asset. def paid_orders(raw_orders): tells Dagster that paid_orders reads raw_orders. When it runs, the IO manager loads the stored value of raw_orders and passes it in. To read an asset under a different parameter name, map it with ins={"orders": dg.AssetIn("raw_orders")}.
deps=[...]. Use it when the downstream asset must run after another but does not need its value in Python, for example when SQL in a warehouse reads the table directly or when an asset only triggers an export. Dagster orders the runs and draws the edge, but loads nothing.
A misspelled parameter is a dependency on an asset that does not exist. Dagster refuses to load the definitions and names the missing input. Dependencies through deps may point at assets outside this code location; they show as external assets.
A data dependency through a parameter, and an ordering dependency through deps.