review-all-gdds

A cross-GDD review identifies contradictions by performing full Markdown reads of every system GDD and running parallel consistency analyses. It detects dependency asymmetries, stale references, tuning-ownership conflicts, and formula mismatches, then outputs a dated review report.

Cross-GDD design holism evaluates multi-system interactions to detect emergent failures like dominant strategies, economic imbalances, cognitive overload, and pillar drift. These design risks only appear when every system GDD is reviewed together rather than in isolation.

Cross-GDD consistency checks are needed during pre-architecture or post-revision review phases. Running a review before building architecture prevents implementation on inconsistent design documents, while post-revision checks catch stale references and acceptance-criteria clashes introduced by recent edits.

Yes, the review process can optionally consult a design/registry/entities.yaml file. Pre-loading the registry provides entity-level context that improves the accuracy of dependency and ownership-conflict detection across system GDDs during the full read phase.

The best way to review tuning and formula compatibility is running a parallel design-theory analysis across all system GDDs. This detects formula range mismatches, tuning-ownership conflicts, and economic imbalances, then generates a dated cross-GDD review report with the findings.

The cross-GDD review does not automatically update the systems index. It offers controlled write and update prompts to the user, allowing you to review the dated report first before approving any optional systems-index updates.