ddd-audit

EXISTING CODE HAS BEHAVIOR. BEHAVIOR WITHOUT DOCUMENTATION IS A GAP. GAPS MUST BE VISIBLE.

Core principle: Brownfield code already has behavior. The audit makes that behavior visible as claims, then checks if documentation supports them.

When to invoke

• Adopting DDD on an existing codebase (brownfield)
• Assessing documentation debt in legacy code
• Producing a coverage report for grandfathered code
• When ddd-book initialization finds existing code without DDD coverage
• When preparing a migration plan from non-DDD to DDD-governed development

When NOT to use

• Greenfield projects with no existing code — use ddd-book to initialize instead
• Code already under DDD governance — use ddd-verify for conformance checking
• A single change's compliance — use ddd-verify