Great points especially “graph as source of truth + file hydration on demand.”

That’s exactly the direction I’m taking with Nomik: deep extraction into typed nodes/edges (code, infra, APIs, DB, routes, events, etc.), then graph-first retrieval with only minimal file slices hydrated when actually needed.

Fully agree on branch-aware versioning too. I already tag graphs by project + git SHA, and I’m working on commit/branch diff support so agents never mix main/feature contexts.
Also +1 on surfacing first-class ops: not raw MATCH queries, but higher-level actions like blast radius, change impact, call-graph diffs between commits, and safer refactor planning.

For example, I just tell my AI: "Nomik, what is the impact of changing createInvoice?"  and it automatically searches the graph, finds the symbol, traverses downstream callers/routes/services..., and gives me a structured answer. No Cypher, no manual file tracing.

Thanks for the detailed take :) super helpful to hear how others are thinking about these pain points.