# $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.GraphIR.description
A complete analytical transformation DAG.

# $defs.HiddenSuiteRef.description
An opaque pointer to a hidden evaluation suite.

subhadipmitra@: Decision: this type carries a locator and nothing else. It has no payload
field and, deliberately, no expected content hash. Publishing that hash inside a
policy-visible artifact is an oracle: a policy able to hash its own candidate output could
self-verify against the hidden suite without ever invoking the hidden validator, and an
unsalted hash over a small fixture pool is also a membership side channel. Hashes live in the
hidden-side index keyed by case id, resolved only by evaluator code. See ADR-018.

# $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.

# $defs.VisibleSuite.description
The validation material a policy is allowed to see.

Provisional: Phase 2 owns the concrete dataset and check shapes. Only the envelope is fixed
here.

# description
One benchmark instance: a starting graph plus its validation material.