consistency-check

To detect cross-document inconsistencies across CDDs, run a grep-first consistency checker that scans all design documents against the entity registry to report conflicts and flag stale registry entries.

A grep-first consistency check is a validation method that scans all CDDs for entity registry entries to detect cross-document inconsistencies, generating conflict reports and flagging registry drift for review.

You should run consistency validation after authoring or updating CDDs, or before holistic reviews, ensuring game and product documentation remains aligned with the entity registry.

Yes, the consistency checker applies to both game and product CDDs, loading the entities.yaml file to validate design integrity and optionally flag stale registry entries for updates.

You can validate specific entities, schemas, or configurations by running an on-demand consistency check that greps your CDDs against the loaded entity registry to identify mismatches.

The best way to keep design documentation aligned is using a grep-first consistency checker that scans CDDs against the entity registry, generating conflict reports and flagging stale entries for updates.