consistency-check

Cross-document inconsistency detection scans registered schemas, APIs, permissions, and configs against matching CDD files using grep-first comparison, classifying hits as conflicts, stale registry entries, or unverifiable references.

Cross-document drift occurs when a central registry and CDD documents fall out of sync, causing architecture and implementation problems. Consistency checks target registered schemas, APIs, permissions, and configs to catch these conflicts before they spread downstream.

You can run a focused lookup to check a single schema, API, permission, or config against the registry. This targeted conflict review avoids a full audit and directly verifies whether the specific entity matches the authoritative CDD source.

Yes, you can run a since-last-review scan to perform an incremental consistency check. This mode evaluates only the updated CDD sections and registry entries, confirming ongoing alignment without the overhead of a full audit run.

The best way to resolve stale registry entries is to follow the registry-correction guidance generated by the audit. The consistency check classifies findings and points directly to the specific CDD documents that need correction to restore alignment.

Yes, consistency checking applies to product and game design documentation review. It compares registered schemas, APIs, permissions, and configs against the relevant CDD files to detect conflicts and unverifiable references across the design architecture.