gpd-regression-check

Automate regression verification by re-validating all previously verified claims across completed phases. The checker reads VERIFICATION.md targets and phase artifacts to detect drift in notation, assumptions, and shared artifacts, returning a consolidated regression report.

Cross-phase consistency checking re-validates previously verified claims to detect regressions after changes. It ensures notation, limits, and shared artifacts remain aligned across all completed research phases by comparing current filesystem-backed evidence against established targets.

Detect notation drift and assumption changes by applying a regression checker to completed phases. It identifies regressions categorized by dimensional issues, symmetry violations, regime violations, and artifact integrity, then generates actionable fixes to restore consistency.

Yes, you need a VERIFICATION.md file along with phase artifacts and filesystem-backed evidence. The regression checker requires access to these targets to re-validate previously verified claims and detect any cross-phase drift or regressions.

Re-validating physics claims detects regressions categorized by dimensional issues, symmetry violations, regime violations, and artifact integrity. The checker analyzes these categories to report actionable fixes and a recommended order to restore cross-phase consistency.

Run a regression check on completed phases whenever changes are made that might affect previously verified claims. This catches regressions early, detects drift in shared artifacts, and ensures cross-phase consistency is maintained before proceeding further.