Prerequisite and dependency mapping

Problem

Future profiler capabilities — such as cross-column correlation detection, lineage-aware semantic typing, and multi-run profile comparison — each depend on foundational infrastructure that doesn't exist yet: a stable column identity system, a profile versioning scheme, a way to reference columns across tables, and possibly SQL lineage tracing. If these prerequisites aren't identified and mapped now, each future feature will independently discover and build its own partial version of the same foundation, leading to duplicated effort and inconsistent implementations. Mapping enabling dependencies while the architecture is still malleable reduces startup cost for future work and allows prerequisite components to be designed with multiple consumers in mind.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared