> (Which is often maintained manually, separate from the repo.) To me, this is the interesting avenue for investigation. Rather than go from visualization ->

> (Which is often maintained manually, separate from the repo.) To me, this is the interesting avenue for investigation. Rather than go from visualization -> code, how can we take an existing visualization that represents some underlying system (a code base, module dependencies, service architecture, a network topology, etc) and easily update the representation as the underlying system changes...