Data Versioning
A query can survive while the data it once returned is lost. Data versioning records the inputs used and the limits on recovering them.
-
-
Metadata Management and Lineage
Scanning a warehouse produces a complete catalog of names and types that answers almost none of the questions people actually arrive with.
-
Impact Analysis
Before changing a column, find everything that depends on it. Lineage finds the pipelines; query logs find the people; neither finds everyone on its own.
-
Column-Level Lineage
Column-level lineage narrows the dependencies to investigate. Its usefulness depends on whether selected fields, filters, joins, and other relevant paths were captured.
-
Versioning Models, Data, Prompts, and Evals
A model version number says little about what the model was built from or what it needs to run. This guide builds a small lineage and registry to show which artifacts a change invalidates, what reproducibility requires, and how promotion and rollback depend on compatibility.
-
Access, Retention, and Erasure Across Data Copies
A deleted row is not an erased person. Follow classification, access rules, retention clocks, derived copies, backups, and audit evidence across a data platform.
-
Metadata and Lineage for Change Impact Analysis
See how run metadata, column-level lineage, coverage measurement, and consumer discovery turn “who uses this column?” into a candidate list you can validate.
-
Data Lineage
Understand how data lineage traces dependencies and supports change impact analysis and error investigation.