gpd-validate-conventions

Physics convention drift occurs when metric signatures, Fourier conventions, or gauge choices change between phases without updating the central lock, which this validation process detects by cross-checking phase artifacts against state.json and CONVENTIONS.md.

Validating metric signature and Fourier convention drift requires loading the convention lock from state.json, scanning completed phase declarations, and reporting mismatches to guide updates to CONVENTIONS.md for reproducibility.

Yes, you can enforce natural units and gauge choices by loading locked conventions from state.json and scanning all completed phases to identify mismatches, aggregating findings to ensure cross-phase reproducibility.

The best way to lock physics conventions and prevent drift is to store them in state.json and CONVENTIONS.md, then run automated validation that cross-checks phase artifacts and reports any deviations from the locked standards.

Your validation reports unlocked conventions because state.json lacks a defined lock for specific metric signatures or gauge choices, meaning the scanner detected phase declarations without a corresponding central standard to compare against.

Yes, deep validation of cross-phase convention artifacts coordinates via subagents to thoroughly scan completed phases, ensuring that metric signatures and Fourier rules match the locked state.json configuration without manual intervention.