# $defs.DependencyEdge.description
A directed dependency between two nodes.

subhadipmitra@: Decision: direction is data flow, from `upstream` to `downstream`. The
downstream node reads the upstream node. The previous `parent`/`child` naming did not state
which way data moved, and a silently inverted lineage graph produces plausible-looking but
wrong results everywhere downstream.

# $defs.Materialization.description
How a model is persisted.

The vocabulary follows dbt because it is the de facto standard for this problem domain. That
is a naming choice only: nothing in this package imports or requires dbt.

# $defs.Provenance.description
Origin record for one serialized artifact.

# $defs.SourceKind.description
Category of input an artifact was derived from.

# $defs.TestAssertion.description
A data-quality assertion attached to a node.

Provisional: `docs/03_SYSTEM_ARCHITECTURE.md` lists tests as a required IR component, so the
slot is reserved now. Phase 2 and Phase 3 own the concrete parameter shapes, which grow
additively under the ADR-009 minor-version rule.

# $defs.TestAssertionKind.description
Category of data-quality assertion attached to a node.

# description
A complete analytical transformation DAG.