c4-model

To document software architecture from a repository, provide the codebase or README to derive Context, Container, and Component diagrams. The process separates confirmed facts from assumptions, validating structure and dependencies to produce self-standing Markdown deliverables with Mermaid or PlantUML diagrams.

Generating C4 diagrams from prose specifications involves applying abstraction-level discipline to clarify system structure. The process transforms ambiguous text into validated C4 model documentation, outputting Mermaid C4, Structurizr DSL, or PlantUML formats with legends, technology details, and documented assumptions.

Yes, you can review and update existing architecture diagrams while preserving their format and destination. The process critiques current C4 diagrams to identify modeling and readability issues, then updates the architecture documentation through structured dialogue and explicit validation.

Yes, the C4 model supports deployment and dynamic views alongside Context, Container, and Component levels. It applies these views to greenfield architecture design and repository retro-documentation, requiring explicit validation, technology annotations, and protocol details for clear system structure.

Designing greenfield software architecture using the C4 model involves co-building views through structured dialogue. It enforces abstraction-level discipline and explicit validation, generating Mermaid or Structurizr outputs with concrete relationship intents, protocols, and documented assumptions.

Supported output formats for architecture diagrams include Mermaid C4, Structurizr DSL, PlantUML, or negotiated alternatives. The deliverables feature legends, technology details, concrete relationship intents, and accompanying Markdown documents to ensure the architecture documentation is self-standing.