Executive summary

LineageSutra AI 0.2.0 answers one question before a schema change reaches production: if I change this column, what breaks, and where is the proof?

The problem

Analytics and data-platform teams rename and drop columns every week. Today the "impact analysis" is a grep, a meeting, or a catalog that is out of date. Mistakes surface as broken dashboards, failed jobs and silent wrong numbers.

The product

An offline command-line tool and 25 portable AI-agent skills. It reads SQL files (or a dbt manifest), builds a column-level lineage graph, and returns:

Why it is different

Typical toolLineageSutra AI
Needs a warehouse connection or SaaS accountReads local files; no network, no credentials, no rows
Shows a graph, hides uncertaintySeparates confirmed from possible and lists unparsed SQL
Claims accuracyPublishes a gold corpus, its labels, and its limits
Opaque outputDeterministic, SHA-256-sealed, reproducible reports

Proof, today

Honest limits

A documented SQL subset, not a certified dialect parser. Static text analysis only. No live-database verification. No independent security review. The SHA-256 seal is tamper evidence, not a signature.

Where it goes next

SQLGlot bridge for dialect depth, OpenLineage import, git-aware schema diffs and signed evidence. See the roadmap.