Temporal and Verifiable Lineage (Point-in-Time)
We know what the lineage looked like on the fiscal year-end — and we can prove nobody touched it.
Framework / standard: ISO/IEC 38505-1 (Principles 5 and 6) · GDPR Art. 5(2)
Your data lineage changes constantly. But when an auditor asks how that KPI was fed on 31 December, most tools only show the current state.
Linedat stores lineage as an append-only event log with snapshots: you can reconstruct the graph at any past date, compare two points in time and do so with verifiable integrity.
Reconstruction at any date
Every graph change (adding or removing a relationship, changing a column mapping, reassigning a domain) is recorded as an append-only event. On top of those events and periodic snapshots, Linedat reconstructs the lineage as it was on any given date and diffs two points in time. You answer point-in-time questions, not just "right now".
Impact analysis before breaking anything
Before dropping a column, bidirectional impact analysis shows you what breaks upstream and downstream. And the change history is cryptographically chained, so the lineage "on that day" is evidence, not a mutable state with no memory.
The limits (what we do not claim)
Lineage is built manually or through the DOT editor; automatic column-level parsing from SQL is not available today. In the temporal OpenLineage export, column-level lineage is not reconstructed (only relationship-level).
How Linedat helps
Linedat lets you answer "how was this KPI fed on the close date?" without archaeology — and prove the history has not been touched.
Related capabilities
Without a contract, every schema change is Russian roulette with someone else's data.
Executable Data Quality (Real SQL, 6 Dimensions)Quality stops being an opinion: rules that execute real SQL against the source, in 8 dialects.
Audit Chain: Verifiable Cryptographic IntegrityOther catalogues store logs. Linedat stores proof — verify it with a button.