architectural-conformance-validation

Architectural conformance validation checks your feature designs and post-implementation code against established ADRs and architecture docs. It outputs a conformance score and structured findings to identify and remediate deviations.

Architectural conformance validation identifies and reports deviations from established architecture decisions and patterns. You need it to prevent architectural drift and misalignment across feature plans, wave designs, and repository implementations.

To check ADR compliance, ensure your Architecture.md and ADRs are accessible as references, then run the validation against your feature design artifacts. It verifies alignment with documented patterns, API contracts, and security data handling.

Yes, architectural conformance validation applies to post-implementation code across the repository. It checks ADR compliance, design-pattern usage, and API contracts to ensure code implementations stay compliant with documented architecture.

Architectural conformance validation covers feature plans, wave designs, and post-implementation code across your project. It produces risk scoring and structured reporting with remediation guidance to maintain architectural integrity at scope.

Validation depends on accessible Architecture.md and ADR references to generate accurate conformance scores. If these reference documents are outdated or incomplete, the automated validation cannot effectively identify architectural drift or verify pattern usage.