Definitions
In plain terms
It lets a learner or auditor trace a displayed value back through source records, code versions, parameters, and corrections.
Technical
Useful lineage captures source identity and version, transformations, inputs and outputs, execution time, responsible agent or system, configuration, and derivation links.
Scope
A source URL alone is not complete lineage, and lineage quality depends on retained granularity.
Examples
- A governed dataset records data lineage explicitly and preserves the source context needed to interpret it.
Common misconceptions
- Data Lineage does not have one universal meaning or policy without its declared source, scope, and data contract.
Concept relationships
Where this concept is used
Tutorials planned
These catalogued topics use this concept, but their complete build has not shipped yet.
- D01-F02-A05 Important
- D01-F04-A03 Important
- D01-F04-A04 Important
- D01-F04-A05 Important
- D02-F03-A01 Important
- D02-F03-A02 Important
- D02-F03-A03 Important
- D02-F03-A05 Important
- D02-F04-A01 Important
- D02-F04-A02 Important
- D02-F04-A03 Important
- D02-F04-A04 Important
Evidence and governance
- PROV-O: The PROV Ontology World Wide Web Consortium · official standard
Supports: preferred label, short definition, technical definition
Limits: It supplies a provenance vocabulary, not a financial-market lineage schema or retention policy.
- Fintech Builder Glossary Definition Contract The Fintech Builder · internal governed contract
Supports: variant distinction
Limits: Defines governed platform behavior rather than claiming these policies are universally prescribed by external McClellan methodology.
- Reviewed by
- Islam Baraka
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published
