A deterministic alternative to embedding-based repo understanding

A CS student built ai-context-map, a prototype that uses static analysis to create a deterministic structural graph of a codebase (files, imports, symbols) instead of relying on embeddings. It outputs a precomputed context map (e.g., .ai/context.yaml) with entry points, core modules, and task routes. The author seeks feedback on whether this graph-based approach can meaningfully reduce token usage and complement or replace embedding-based repo understanding.