consistency-check

Cross-document inconsistencies are detected by comparing GDD definitions against a central entity registry of entities, items, formulas, and constants to identify conflicting values across multiple documents.

A grep-first targeted scanning approach loads the authoritative entity registry once, then searches only relevant GDD sections by registered names instead of fully rereading every document to extract conflicts efficiently.

Run a consistency check by loading the design/registry/entities.yaml file and scanning all registered entities against your GDDs, using full or scoped modes to generate conflict, stale, and unverifiable reports.

Yes, you can use scoped modes to check specific sections of your game design documents, performing precise section reads to confirm which document is authoritative and exactly what diverged from the registry.

Checking GDD registry conflicts generates actionable conflict reports for resolution, flags stale registry entries, marks unverifiable mentions lacking comparable attributes, and outputs session logging.

Stale registry entries occur when the central entity registry contains definitions no longer actively supported or matched within the current game design documentation, which are flagged during the consistency check.