When an Agent Touches Your Data, Lineage Is the Alibi
A risk manager once walked over to my desk holding a printout. One number on it was circled. Not wrong, exactly. Just different from the number on the same report the day before, and nobody had changed anything. I spent most of that afternoon working backwards. The report read a view, the view read a table, the table was loaded by a job, the job pulled from a vendor file, and the vendor had…
In a story about data lineage, a risk manager spent an afternoon investigating a discrepancy on a report. The report had a circled number that differed from the previous day's version, despite no changes being made. The manager worked backward to trace the source of the discrepancy. This experience highlights the importance of lineage as an alibi in tracking data changes. Lineage provides a record of the data's journey, including the run, script, source, and actor responsible for each step.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
