system-architect

To generate Mermaid architecture diagrams from an approved specification, you apply C4 diagrams, data models, and sequence diagrams to capture the system's structure and feature flows. Artifacts are produced only when a spec is approved or a decision requires documentation.

You need to create an Architecture Decision Record (ADR) when a meaningful architectural decision requires documentation to capture trade-offs and rationale. ADRs ensure a single source of truth that teams can reference during the system's evolution.

Yes, this approach supports versioning architecture artifacts in Git workflows by storing them in Mermaid format. This enables diffable history and reviews, ensuring architecture artifacts remain up-to-date, versioned, and discoverable.

The best way to document system architecture and its evolution is maintaining versioned Mermaid diagrams and ADRs. This captures C4 containers, data models, feature flows, and API documentation, ensuring stakeholders reference a single source of truth.

Yes, you can use C4 diagrams and sequence diagrams together to visualize feature flows. This combination captures the system's architecture alongside specific feature interactions, translating complex designs into clear Mermaid diagrams for engineers.