EQTY LabDocs

Lineage Graphs

Lineage manifests registered by the EQTY SDK, and the lineage graphs Integrity Service serves from them.

View as Markdown

Lineage graphs show how a dataset, model, or other asset was produced. The EQTY SDK registers each graph and its lineage manifest with Integrity Service, which stores the manifest’s statements and blobs so the graph can be verified later. Lineage is separate from the governance evidence behind policies: declarations, reviews, and credentials are recorded in policy manifests.

When Users See Lineage

Users normally inspect lineage from Guardian. The Lineage Graphs view appears when lineage is enabled for the deployment and the project has lineage records to display.

What a Lineage Graph Helps Answer

  • Which inputs, code, and configuration produced a model or dataset?
  • Which computation connected an output to its inputs?
  • Has each step’s record been verified?
  • Is there enough context to understand how an asset was derived?

Good Practices

  • Review a model’s or dataset’s lineage before relying on it as evidence for a control.
  • Confirm that the graph belongs to the expected project.
  • Treat missing lineage as a signal to check feature enablement, permissions, or service health.
  • Use lineage as supporting context, not as a replacement for reviewer judgment.