Answer whether an asset's declared lineage held up under runtime capture.

This is the question Polygraph exists for. Returns the verdict Polygraph reached, the evidence behind it, and an explicit statement of what the verdict does and does not establish.

Get the Lineage Integrity Score for a job, with its components.

The score is the Jaccard index of declared vs observed edges. Precision and recall are returned separately because a low score from stale claims and a low score from missing sources need different fixes.

List assets the runtime reads that the catalog never declared.

These are usually the most consequential findings: nobody reviewing the catalog could have known these assets are inputs.

List declared lineage edges that carried no data in the captured run.

Usually stale declarations left behind by a refactor. A genuinely conditional edge whose branch was not taken looks identical, so these need human judgement rather than automatic deletion.

Retrieve a Polygraph incident report from DataHub's knowledge base.

Incident reports name the operation responsible for a model-quality collapse, the owning team, and the real before/after metrics.

Explain exactly what Polygraph's three verdicts mean and do not mean.

Call this before presenting verdicts to a person. The verdicts are easy to overstate, and overstating them is the failure mode Polygraph exists to prevent in the first place.