In Part 1, I explained why Enola extracts deterministic architectural facts before an AI agent begins reasoning. That leaves the next design question: How should those facts be represented? The obvious answer is to build a graph containing every symbol, dependency, route, service, and repository.
Source: [Dev.to](https://dev.to/gert_/building-enola-part-2-from-source-code-to-an-architectural-fact-model-djm)