mcaf-architecture-overview

You create architecture maps for onboarding by generating docs/Architecture/Overview.md with Mermaid diagrams. This maps boundaries, dependencies, and contracts to establish a shared architecture overview for teams.

The best way to document module boundaries during refactoring is updating Overview.md with Mermaid diagrams. This ensures dependencies use real names with explicit links and references relevant ADRs.

Yes, you can map system interfaces and contracts using Mermaid diagrams. The architecture overview generates specific diagrams for the system/module map, interfaces/contracts map, and key classes/types map.

Yes, architecture documentation explicitly links to ADRs and features. It ensures diagrams use real names with explicit links while documenting dependency rules and ADR references.

You should update architecture overview documentation when onboarding, refactoring, or adding modules and boundaries. This orients teams and maintains a shared architecture map reflecting current system contracts.

Start documenting dependency rules by opening docs/Architecture/Overview.md and updating the Mermaid diagrams. This reflects current boundaries and dependencies while establishing explicit dependency rules.