Show HN: Enola-A deterministic architecture graph for developers and AI agents
Together with a friend, we were developing a golf application. Our codebase grew rapidly and became split between multiple repositories: the iOS app, Android app, backend, front-end, and extra tooling. Both of us also work in larger scale-ups, and we saw the same problem: understanding large distributed codebases becomes progressively harder. Yay for microservices. It takes time to understand and answer questions like: - What calls this function? - What is the impact of changing this interface?