reversa-architect

You generate C4 diagrams and ERD models by synthesizing scattered reverse-engineering findings into traceable architectural documentation. This process consolidates artifacts from your output folder into structured markdown covering C4 Context, Containers, Components, and full ERD modeling.

A spec impact matrix documents external integrations and maps which architectural components are affected by specific specifications. It provides traceability across legacy systems, showing the direct impact of requirements on the synthesized architecture overview.

Yes, you can identify technical debt during architecture synthesis by detecting inconsistencies and missing coverage signals in the reverse-engineering artifacts. It highlights likely technical debt areas to ensure the rebuilt architecture avoids existing structural flaws.

You consolidate reverse-detection findings by reading the doc level from your state configuration and writing specified markdown outputs to the configured output folder. This synthesizes context artifacts into an architecture overview ready for decision-making.

Yes, the architecture documentation includes ERD coverage by generating a full Entity Relationship Diagram in Mermaid format. This complete data modeling is also summarized within the architecture overview when applicable to the legacy system.

A limitation is that producing C4 Container and Component diagrams requires enabling higher generation levels, as only C4 Context is generated by default. Additionally, the synthesis depends entirely on the completeness of prior reverse-detection artifacts in your context folder.