2 min lesson
Lineage is impact analysis
Use "Without lineage you find out by getting paged by each downstream owner in turn" to describe the practical rule.
Step 1 of 2
Lineage is impact analysisthe difference between a 5-minute and 5-hour incident
When a bronze table breaks, the first question is who consumes it. Without lineage you find out by getting paged by each downstream owner in turn. With lineage you query the graph, see the eleven silver assets and the one revenue dashboard hanging off it and decide blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. in one look. The same graph shows who will feel a schema change before you make it, and it lets a stakeholder ask where a number came from and get a real answer.
An agent can walk that graph for you. A finance team hit discrepancies in a revenue-recognition booking table that sits downstream of five or six upstream tables plus the jobs running between them. They pointed Cursor at the bad number and it traced the reconciliation issue back up the chain: which tables feed which, which jobs produce which outputs, whether snapshots existed and which PRs changed how each table gets built. It walked the whole history to the furthest upstream source.
This is the senior version of root cause: knowing lineage exists is the start, and using an agent to traverse it across tables, jobs, snapshots and the PRs that changed them is the finish.
"We're actually able to trace back the reconciliation issues all the way back to the furthest upstream table using Cursor."