lineage

DE//AGENT currently lists 11 resources under lineage: 5 tutorials, 2 references, 1 skill. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Also present: 1 mcp server, 1 plugin, 1 agent.

Documented learning objectives across these resources:

• Read the lineages of an asset from a lineage store — via Lineage Explainer
• Compute a downstream impact set — via Lineage Explainer
• Distinguish technical from business lineage — via Lineage Explainer
• Explain why column-level lineage beats table-level for change impact — via Column-level lineage: the concepts and the event standard
• Read an OpenLineage event and name its Airflow, Spark and dbt integrations — via Column-level lineage: the concepts and the event standard
• Compute a downstream impact set from a lineage store — via Column-level lineage: the concepts and the event standard
• Classify a breach by clause — schema, semantics, or SLA — via Respond when a data contract breaks
• Bound the consumer impact set from lineage before assigning the fix — via Respond when a data contract breaks

10 more objectives live on the individual resource pages.

These resources map to stages: Observability (10), Data Quality (1). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. DataHub MCP Server score 42.2 — intermediate
2. Lineage Explainer score 35.5 — intermediate
3. Column-level lineage: the concepts and the event standard score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Data Catalog Assistant.

Security-flagged entries: DataHub MCP Server (2 flags), Lineage Explainer (2 flags), Incident drill: a broken upstream caught by freshness and lineage (2 flags), Lineage tooling in practice: DataHub MCP and the lineage-graph plugin (2 flags), Data Catalog Assistant (2 flags), Lineage Graph (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• DataHub MCP Server — Exposes a DataHub catalog: search entities, read lineage and schema, and inspect metadata, so an agent can answer "what is this table and what depends on it?". details
• Lineage Explainer — Traces column-level lineage from an asset to its upstream sources and downstream consumers, and reports the impact set for a proposed change. details
• Column-level lineage: the concepts and the event standard — Table-level lineage says a job touched a table; column-level lineage says which columns feed which. Learn the concepts, the OpenLineage event model that makes lineage work across t… details
• Respond when a data contract breaks — Work the broken-contract runbook end to end: identify which clause broke, bound the consumer impact set from lineage before anything else, decide whether the producer reverts or th… details

Real install commands from the registry — read the source before running any of them:

uvx mcp-server-datahub

DataHub MCP Server — review first

npx de-agent-platform add lineage-explainer

Lineage Explainer — review first

amp plugin add de-agent/lineage-graph

Lineage Graph — review first

Adjacent topics: tutorial (5 shared), impact-analysis (5 shared), metadata (3 shared), catalog (3 shared), docs (2 shared), mcp (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.