The lineage (dependency) model introduced on August 21, 2026 is a significant step forward and has proven highly effective across multiple sample scenarios I tested. The current implementation, which establishes lineage based on Source Table to Target Table mappings, provides clear visibility into structural dependencies. However, one limitation I have observed is that variable-driven transformations are not yet represented in the lineage. For example, audit column assignments such as create_date = now() or metadata attributes in hub/satellite models like record_source and hash_diff are excluded from the dependency graph. Capturing these derived values would greatly enhance the completeness of the lineage model, ensuring that both structural and semantic dependencies are traceable. Incorporating this capability would make the feature exceptionally powerful, and I am eagerly awaiting its inclusion in future updates.