enrichment schema 2

plan-extended-anaylis/architecture.md

@@ -39,6 +39,13 @@ The State Machine Exporter now becomes a "Consumer" of intelligence.
 - **Maintainability**: Adding support for a new framework (e.g., Micronaut) only requires updating the `IntelligenceProvider`, not touching the core state machine logic.
 - **Performance**: We can run the SM Parser and the Intelligence Scanner in parallel since they are now independent.
 
+## 5. Monorepo and Multi-Module Support
+Applications are often split into multiple modules (e.g., `core`, `api`, `workers`).
+- **Workspace Scanning**: The analyzer should treat the entire monorepo as a single codebase context.
+- **Source Tracking**: Each metadata item (`TriggerPoint`, `EntryPoint`) includes a `sourceModule` identifier to show exactly where it was found.
+- **Cross-Module Resolution**: Properties defined in one module's `application.yml` and used in another should be resolved globally.
+- **Internal Dependency Following**: If the analyzer finds a call to a method in another module, it should continue the call-chain analysis into that module's source.
+
 ## Challenges
 - **Multiple State Machines**: How to know which `StateMachine` instance is being used?
   - Initial heuristic: If there's only one, assume it's that one.