Customer LTVLooker · 2 hops · column evidence
exact column-lineage evidence · business-intelligence surface
80
Schema changes without blind spots
LineageGuard turns one proposed field change into deterministic risk, owner actions, review artifacts, and a structured handoff record.
At least one dataset-level path needs owner confirmation.
03 · Review bundle
Generated content is reviewable evidence—not an automated migration.
# LineageGuard impact report **Decision:** `BLOCK_AND_MIGRATE` · **Risk:** 92/100 (critical) · **Confidence:** partial_catalog_evidence Proposed change: `rename` of `customer_id` on `ORDER_DETAILS`. | Downstream asset | Platform | Hop | Evidence | Risk | Owner | | --- | --- | ---: | --- | ---: | --- | | Customer LTV | Looker | 2 | column | 80 | Lina Ortiz | | fct_orders | dbt | 1 | column | 80 | Noah Patel | | finance_order_replica | Snowflake | 1 | column | 80 | Ari Jones | | Revenue pulse | Power BI | 2 | dataset | 71 | unassigned | The report is advisory. Generated SQL is not executed by LineageGuard.
04 · Human handoff
LineageGuard preserves this plan in a structured decision record so the next engineer—or agent—can inherit the evidence.
Lina Ortiz: acknowledge customer_id → buyer_id migration for Customer LTV.
Noah Patel: acknowledge customer_id → buyer_id migration for fct_orders.
Ari Jones: acknowledge customer_id → buyer_id migration for finance_order_replica.
Assign an accountable owner for Revenue pulse before contract phase.