Dependencies decide what waits for what. a >> b means b runs after a; b << a says the same thing. A list fans out or in: start >> [load_north, load_south] >> publish runs both loads after start, side by side, and publish after both. Python cannot put >> between two lists, so for longer shapes use chain from airflow.sdk: chain(a, [b, c], [d, e], f) links b to d and c to e pairwise, so the two lists must be the same length.
TaskFlow calls and classic operators mix freely: the reference an @task call returns supports >> too.
The graph must be acyclic. If a chain of arrows leads back to a task already on it, the file fails to import with "Cycle detected" and the whole Dag disappears from the list until you remove the edge that closes the loop. The Graph view is the quickest way to see the shape you wrote.
A fan-out and fan-in. The two loads run at the same time.