consistency-check

To check design inconsistencies across GDDs, compare entries in the central entity registry with GDD markdown files using targeted grep scans. This detects mismatched entity, item, formula, and constant definitions to prevent architecture errors.

Grep-first conflict detection scans quickly locate only relevant GDD sections mentioning registered entity names, minimizing I/O while identifying mismatched definitions between the registry and design documents.

Yes, you can run an incremental consistency check on a specific entity. The system supports full project scans, incremental scans since the last review, or targeted single-item checks to locate relevant GDDs and detect conflicts.

You should scan your entity registry against GDDs after each GDD edit or before architecture generation. Running consistency checks at these points keeps the design system in sync and prevents wasted review cycles.

The best way to resolve mismatched constant definitions is to generate a concise conflict report after scanning. This report highlights mismatched values and suggests registry corrections or document updates to synchronize the design.