agw-compliance-review

To enforce architectural compliance, you must validate project analysis against Architecture Decision Records and readiness criteria. This gatekeeping process verifies all ADRs are addressed and open questions are resolved before transitioning to the implementation phase.

An Analysis-Gated Workflow prevents architectural drift by enforcing a rigorous compliance gate between analysis and implementation. It requires systematic verification of ADR status and formal documentation of compliance iterations before allowing phase transitions.

Verify ADR compliance by tracking and validating that all Architecture Decision Records have documented compliance responses. This readiness assessment checks the analysis against a strict Definition of Ready to prevent premature advancement to coding.

Run a compliance review when you have completed initial feature and code analysis and need to ensure your proposed solution strictly adheres to the Software Architect's constraints and ADRs before writing any code.

Yes, a compliance gate requires the resolution of all open questions before implementation. It operates by demanding formal documentation of compliance iterations and systematic verification of ADR status to ensure full architectural alignment.

The best way to track ADR status is through an automated compliance enforcement process that validates pending Architecture Decision Records against project analysis and documents readiness to prevent premature implementation.