Protocol
Carry data lineage through derived outputs
A number without lineage is difficult to debug once it becomes important.
When it fits
- A table, dashboard, model input or exported file is derived through several data-processing steps.
When to avoid it
- Complete lineage can be expensive; prioritize data whose errors would affect important decisions, compliance or recovery.
Why it matters
For consequential derived data, record the source snapshot, transformation version, material filters or joins and output identity. Propagate the lineage reference into downstream artifacts so an anomalous value can be traced back to the exact input and processing path. Treat manual edits as transformations too.
Steps
- The exact source snapshot or extraction time is identifiable.
- Transformation code or rule version is recorded.
- Material filters, joins or manual edits are visible.
- The output has a stable identity.
- Downstream consumers retain a link to the lineage record.
An example
A KPI workbook records the source query revision and extraction timestamp so a suspicious total can be reproduced after the source table changes.
Check your result
A reviewer can reproduce or explain a derived value without guessing which source version and transformation produced it.
Keep this limit in mind
- Complete lineage can be expensive; prioritize data whose errors would affect important decisions, compliance or recovery.
Connected ideas
Useful withReconcile what changed after a bulk write
Evidence and sources
The 2026 provenance-neglect paper defines provenance broadly as the recorded history of data origin, collection, transformation, processing and handling over time.
The paper adapts provenance concepts to news verification; other domains may require additional lineage fields.
The Original Sins of Algorithmic Authenticity Verification: Provenance Neglect and Model Collapse in AI-Mediated News and Information · Definition of provenance neglect and data provenance
Current C2PA specifications use ingredients and actions to represent how prior assets contribute to a new asset and how it was transformed over time.
A complete semantic data-lineage system may need domain-specific transformations beyond media-oriented C2PA assertions.
Content Credentials Specification 2.4 · Assertions, actions and ingredients