Impact Analysis
Impact reports are derived from the same hash‑chained ledger that drives lineage. Every report writes an ImpactAnalysisRun entry pinned to the ledger ULID it was computed against — so a stakeholder review is reproducible months later.
Before making a change to any schema element, Magellan shows you exactly what depends on it — downstream mappings, dashboards, reports, and teams.
Impact analysis traces through the full lineage graph to surface both direct and transitive dependencies that might be affected by a proposed change.
This enables confident schema evolution: teams can assess the blast radius of a change before committing to it, reducing the risk of breaking downstream consumers.
Each report writes an `ImpactAnalysisRun` entry recording the proposed change identifier, the ledger ULID the analysis was computed against, and the result hash. Re-running the analysis at the pinned ULID is guaranteed to produce the same result.
Impact reports can be exported and shared with stakeholders, making change management a collaborative and transparent process.
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.
ImpactAnalysisRunImpactReportExportedRelated 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