consistency-check

Detect cross-document inconsistencies by scanning game design documents against the entity registry. The tool targets GDD sections mentioning registered names, compares extracted attribute values, and deep reads only confirmed conflicts to flag mismatches like divergent stats or formulas before implementation.

Validating entity registry entries against multiple GDDs works best with a grep-first scanning approach. It loads the registry once, targets only relevant document sections to minimize I/O, and classifies results into conflicts, stale entries, and unverifiable mentions for targeted resolution.

Yes, you can run an incremental consistency check since the last review of your design documents. The tool supports multiple modes including full-project audits, since-last-review incremental scans, and focused per-entity investigations to catch design contradictions efficiently without rescanning everything.

The consistency check expects an entity registry file at design/registry/entities.yaml by default. It uses this canonical YAML file to compare extracted attribute values from your game design documents and optionally propose safe registry updates with provenance notes.

Mismatched constants and formulas propagate into downstream architecture docs because scattered game design documents diverge from the canonical entity registry over time. Running a registry comparison scan after authoring new system GDDs catches these design contradictions before architecture or implementation work begins.

Unresolved issues found during a game design document audit are appended as structured failure entries to the reflexion log when present. The tool also offers to update registry entries with provenance notes for confirmed conflicts, ensuring a clear audit trail for downstream resolution.