[lum1104]

One thing I realized while working on large repos is that most “code graph” tools are still fundamentally navigation tools.

You can see structure, dependencies, call graphs, etc., but you still spend a lot of time manually building a mental model of why things exist and how concepts connect across the codebase.

What I’m trying to explore with Understand Anything is whether LLMs + structured graphs can help generate higher-level semantic understanding instead of only visualization.

For example:

1. tracing how a business concept propagates through services/modules 2. mapping requirements ↔ implementation ↔ data flow 3. surfacing architectural patterns automatically 4. helping new contributors build a mental model faster

Still very early obviously, but that’s the direction I’m interested in exploring.

[rkagerer]

“code graph” tools are still fundamentally navigation tools

Yeah, the first thing I noticed in this project's screenshots are a bunch of boxes scattered all over a canvas. Documentation someone truly put effort into would have those boxes grouped in sensible affinities.

Documentation is a very human facing craft - i.e. the aim you strive for throughout is for the reader to understand the system and design intent it reflects. To convey your mental model or give them the primitives to build their own.

So many junior devs I encounter don't initially understand their role as a documenter is to be an educator.