Learn
provenance
2 registry resources · 1 tutorial, 1 skill · roadmap: Observability
What this topic covers
DE//AGENT currently lists 2 resources under provenance: 1 tutorial, 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.
What you can learn here
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
Where this fits in the learning roadmap
These resources map to stage: Observability (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.
Compare the registry's options
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.
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| Lineage Explainer | Skill | intermediate | community flags | 35.5 |
| Column-level lineage: the concepts and the event standard | Tutorial | intermediate | community | 34.15 |
How scores are computed: source quality score.
Where to start
Highest composite score first:
- Lineage Explainer score 35.5 — intermediate
- 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.
Cautions and limitations
Security-flagged entries: Lineage Explainer (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.
Production use cases
- 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
Install and inspect
Real install commands from the registry — read the source before running any of them:
npx de-agent-platform add lineage-explainerLineage Explainer — review first
Further study
Adjacent topics: lineage (2 shared), impact-analysis (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.
Full resource list
| Resource | Type | Score |
|---|---|---|
| Lineage Explainer | Skill | 35.5 |
| Column-level lineage: the concepts and the event standard | Tutorial | 34.15 |