drift-detection

Codebase drift is cumulative divergence that slips through per-commit gates. Periodic drift scanning detects it by surfacing actionable findings across seven indicators, including identifier, contract, and layer drift, to align mental models with the evolving codebase.

To detect cumulative drift during a release candidate review, run a periodic drift scan to generate a report. This report lists actionable indicators and patterns across contract, test, and defaults drift to guide method evolution and loop-driven engineering decisions.

You can scan for seven drift indicators in your codebase: identifier drift, contract drift, layer drift, doc-model drift, rubric drift, test/spec drift, and defaults drift. These indicators surface actionable patterns to guide documentation hygiene and method evolution.

Yes, periodic drift scans improve documentation hygiene and test specs. The scan surfaces doc-model drift and test/spec drift indicators, producing actionable findings that guide loop-driven engineering decisions and method evolution.

Drift detection does not replace per-commit code quality gates. It complements them by performing periodic scans on a weekly cadence to surface cumulative divergences and long-term patterns that slip through standard per-commit checks.