dld-audit

To detect code drift from documented decisions, you can scan your codebase for discrepancies between code annotations and decision records. This process identifies orphaned annotations, stale references, and undocumented changes by tracking modifications since the last audit.

Decision logging drift occurs when actual code changes no longer align with their intended documented reasoning. This discrepancy creates technical debt because developers may rely on outdated decision records or orphaned code annotations that fail to accurately reflect the current codebase state.

You validate code annotations against decision records by running an audit script that compares active annotations with existing records. This checks if decision records reference removed code and ensures all annotations correctly map to accepted decisions after a series of refactors.

Yes, dld-audit requires git and shell scripting for execution to scan for orphaned code annotations. It relies on git to track modifications since the last audit and identify undocumented changes within your codebase.

You find stale references and undocumented changes by running an audit that compares code annotations against decision records. This scan identifies discrepancies where decision records point to removed code or where recent code modifications lack proper decision documentation.

The best way to maintain decision records during refactoring is to run regular drift detection audits. By scanning for orphaned annotations and validating references, you ensure your documented decisions consistently align with the actual codebase and prevent accumulated technical debt.