consistency-check

To find cross-document inconsistencies, compare all GDDs against the entity registry using a grep-first workflow. This approach reads the registry once and targets only sections mentioning registered names, surfacing conflicts efficiently without requiring full document reads.

A grep-first conflict detection workflow reads the entity registry once, then searches GDDs for registered names to locate mismatches. It avoids full document reads unless a specific conflict needs investigation, ensuring source-of-truth alignment across items, formulas, and constants.

Check your entity registry for stale entries by running a consistency-check after creating or updating a GDD. This generates a structured consistency report that tracks registry staleness, identifies conflicts, and provides guidance for resolving source-of-truth mismatches.

Yes, consistency-check works without external dependencies. It uses a grep-first approach to scan registered entities, items, formulas, and constants across multiple GDDs, requiring only the entity registry file and the design documents to operate.

Run a consistency report immediately after creating or updating a GDD. This surfaces cross-document conflicts early, tracks stale registry entries, and provides structured guidance for potential corrections to both the GDDs and the registry.

The best way to enforce source-of-truth alignment is using a grep-first scanning workflow against the entity registry. This targets registered names across GDDs, detects conflicts without full reads, and generates a structured report with potential corrections.