ddd-drift

DRIFT IS INEVITABLE. UNDETECTED DRIFT IS A SILENT CONFORMANCE FAILURE.

Core principle: Evidence, docs, and code drift apart over time. Detecting drift early prevents silent conformance failure.

When to invoke

• Scheduled drift check (CI cron, pre-commit, or on-demand)
• After external documentation updates (vendor docs, standards)
• After significant code changes outside DDD scope
• When troubleshooting unexplained behavior
• Before releasing a new Book version

When NOT to use

• As a substitute for compliance verification — use ddd-verify for change-level checking
• For a single change's conformance — drift is systemic and scheduled, not per-change