Guide
Review architecture drift without turning it into a style debate.
Architecture review works best when findings stay tied to evidence, categories, and concrete recommendations.
Look for evidence first
Start from audit detail and tool report cards. Confirm which architecture reports exist before treating missing report data as a signal.
Use recommendations as review inputs
Recommendations should help reviewers ask better questions about module boundaries, ownership, dependency direction, and release impact.
Keep related pages close
FAQ
Does Audit Sherpa prescribe one architecture?
No. It helps review report-backed findings against the standards your team already uses.
Can architecture findings be grouped?
Dashboard recommendations can be reviewed by repository, source tool/category, or priority where data supports it.