consistency-check

You can run an automated consistency-check to validate GDDs against the entity registry. It uses a Grep-first approach to locate mismatches by pattern matching, identifying conflicting values, stale entries, or unverifiable references without scanning entire files.

The best way to find stale registry entries and conflicting values is to use a consistency-check tool that classifies discrepancies into concrete categories. This categorization guides fixes by helping you decide which document should be the source of truth and when to update the registry.

Yes, you can validate a specific entity or item without checking the whole registry. The consistency-check supports targeted inspection modes like entity:<name> and item:<name>, allowing you to perform deep-dive triages and focus only on sections mentioning specific registry entries.

Grep-based validation minimizes full-file scans by using pattern matching to search across design and GDD directories. This approach focuses solely on sections that mention registry entries, quickly locating mismatches without the overhead of reading entire documents.

To identify the source of truth after finding cross-document conflicts, you review the audit-ready reports generated by the consistency-check. These structured findings classify discrepancies and provide guidance for when to align the registry with the source GDDs.

Yes, the consistency-check workflow supports incremental reviews. It includes a since-last-review inspection mode, allowing you to scope the cross-document validation to only recent changes rather than performing a full scan of all design artifacts every time.