ce-adr-gap-analyzer

To verify code compliance with architecture decision records, you analyze repository source code, tests, and docs against ADR intent. This identifies evidence-backed gaps with file and line pointers, producing a dated gap report for unresolved items.

ADR gap analysis extracts decisions from architecture decision records and maps them to realized code and documentation. It surfaces misalignments between intended architecture and actual implementation, producing evidence-backed gaps for remediation.

Generate an ADR compliance report by sweeping a single ADR or all appendix records to verify implementations satisfy stated decisions. The output includes severity scores, evidence-backed gaps, and a stamped compliance line for the ADR status appendix.

Yes, you can analyze a single ADR by targeting a specific record like ADR-004. The analyzer reads the individual ADR text, extracts its decisions, and checks the relevant code, tests, and documentation for compliance gaps.

The best way to update ADR status appendices is to run a compliance verification sweep across the repository. This produces a stamped compliance line and a dated gap report to append, ensuring governance reflects the current implementation state.

Your software implementation diverges from documented architecture decisions when code and tests evolve without updating the ADR or RTD. A gap analysis maps the intended decisions to the current codebase, highlighting unresolved misalignments with severity scores.