Quant Memo
Core

Data Lineage and Provenance

Data lineage is the traceable record of where every number in a research pipeline came from and what transformations produced it, and without it a discovered bug in a data source can't be traced to which results it corrupted.

A backtest result depends on a chain of data: raw prices, corporate action adjustments, a universe filter, a feature calculation, a model, and finally a P&L number. Data lineage is the record of that whole chain — which raw source fed which transformation, in what order, at what time — so that if a number looks wrong, someone can trace backward to find exactly where it came from, and if a source turns out to be wrong, someone can trace forward to find every result it touched.

Without lineage, a quant discovering that a vendor's dividend field was silently backfilled with a wrong value has no way to know which of the firm's hundred running backtests used that field, whether the error affected live trading decisions, or whether it's safe to keep trusting other fields from the same vendor. With lineage tracked — even something as simple as tagging every derived dataset with its source dataset's version and timestamp — that same discovery becomes a fifteen-minute query instead of a firm-wide fire drill.

Data lineage turns "which of our results are affected by this bad data?" from an open-ended investigation into a traceable query, which is why it matters far more once a firm runs dozens of pipelines than when a single researcher runs one script.

Provenance also matters for research integrity on its own: a result that can't be traced back to its raw inputs can't be independently reproduced or audited, which is exactly the property a golden dataset or regression test is designed to protect.

Related concepts

Practice in interviews

Further reading

  • Buneman, Khanna & Tan, 'Why and Where: A Characterization of Data Provenance'
ShareTwitterLinkedIn