Automated Lineage
Lineage is derived from the audit ledger, not reconstructed after the fact. Every discovered edge writes a LineageEdgeDerived entry — so the lineage graph an auditor sees is the same graph the application uses, with the same hash chain backing it.
Magellan traces data flows from source systems through transformation pipelines to downstream consumers — automatically.
It documents how each field in a target dataset connects back through intermediate transformations to its original source columns.
Lineage edges are derived from ledger entries, not inferred from a separate scan. When a `MappingDrafted` or `MappingRevised` entry lands, the lineage projector emits a `LineageEdgeDerived` entry — both keyed by ULID, both chained — so the lineage view is reproducible from the ledger alone.
This automated lineage eliminates the tedious manual work of documenting data flows and keeps lineage documentation current as pipelines evolve.
Stakeholders can use lineage information for regulatory compliance, root‑cause analysis, and impact assessment before making changes — and the lineage they see is provably the lineage the system acted on.
Audit ledger entries written by this feature
Each action in this feature appends one of the following entry types to the ULID‑keyed, SHA‑256 hash‑chained audit ledger. A reviewer can replay the chain to reconstruct exactly what happened, when, and under which role.
LineageEdgeDerivedLineageProjectionRebuiltRelated glossary terms
Definitions for the technical, regulatory, and standards terms referenced on this page. Each link opens the term in the full glossary.
Open the full glossary