reversa-architect

Generate architecture documentation by synthesizing reverse-engineered legacy artifacts into C4 diagrams, an ERD, and an integration map. This process translates raw discovery findings into coherent, audit-ready system architecture outputs for downstream design.

A Spec Impact Matrix maps which components affect which spec elements to improve change governance and drift analysis. You need it when interpreting legacy systems to ensure traceability between architectural components and specification requirements.

Yes, you can create C4 context and container diagrams from existing codebase discoveries. The synthesis process generates these diagrams based on doc_level, producing Mermaid documentation files that capture the system's structural and contextual architecture.

Map external integrations by synthesizing discovered artifacts during the interpretation phase. The process generates an external integration map that explicitly defines connections between the legacy system and external dependencies for architectural review.

The process produces Mermaid documentation files stored in the _reversa_sdd directory by default. These files include C4 context, containers/components diagrams, an ERD with relationships and keys, an integration map, and a Spec Impact Matrix.

Yes, generation is driven by reading .reversa/state.json and artifacts in the output and .reversa/context/ directories. This state file specifies the output folder and provides the necessary context for synthesizing the architectural documentation.