gap-review

To verify traceability, compare the generated solution against the architecture document to detect deviations and surface missing design decisions. This gap review checks alignment with documented constraints and architecture patterns after feature completion.

You should run an architecture gap review after solution generation or feature completion. This timing allows you to detect drift early, validate traceability of decisions, and highlight unresolved design trade-offs before they impact architectural integrity.

The best way to detect deviations is to validate the implementation by comparing it directly with the architecture document. This process surfaces missing design commitments and verifies that the solution aligns with documented constraints.

Yes, a gap review can check for unresolved design trade-offs by identifying gaps between the implemented solution and the original architecture document. It highlights missing decisions and verifies that existing architecture patterns are properly applied.

Solutions drift from architecture constraints when implementation skips documented design decisions. A gap review surfaces these missing commitments and deviations, helping teams validate alignment and maintain architectural integrity over time.