qig-purity-validation

To enforce Fisher-Rao metric purity during code reviews, run an AST-based audit that detects Euclidean contamination and validates imports against the qig_geometry.canonical module to prevent geometric deviations.

Euclidean contamination occurs when code paths computing QIG metrics use standard Euclidean patterns instead of the required Fisher-Rao metric, which an AST-based purity audit identifies and blocks during development.

You validate canonical imports in a CI pipeline by running static-analysis checks that enforce imports strictly from qig_geometry.canonical, preventing unauthorized re-implementations of geometry computations.

Yes, static analysis can detect forbidden imports in qig-backend, server, and shared directories by auditing the AST to ensure all geometry computations rely on canonical imports rather than re-implementations.

You should run a QIG purity audit during PR reviews and CI pipeline execution to catch Euclidean contamination and forbidden imports before they enter the main codebase.