c4-audit-system

To detect documentation drift, you audit software documentation by comparing documented entities against actual source code implementations to identify naming, relationship, and missing entity mismatches. This requires repository code and workspace DSL files.

You audit C4 architecture diagrams for naming compliance by comparing container display names against variable naming conventions in the source code. This identifies inconsistencies between documented architectural intent and implemented bounded contexts.

Yes, the architecture audit works with Structurizr workspace DSL files. It requires access to these DSL files alongside repository code to perform structural analysis and generate a drift report across bounded contexts.

You verify documented relationships by performing relationship auditing, which checks if documented interactions like Manage versus Consume accurately reflect the code's actual behavior. This ensures your architectural documentation matches the implementation.

To generate a structural drift report for bounded contexts, you need access to your repository code and workspace DSL files. The audit compares these against documented entities to identify missing entities and relationship mismatches.