ast-first-gate

To enforce AST dependency graph analysis before refactoring code, you need a fail-closed gatekeeping mechanism that blocks all code modification until the graph is built, documented, and validated. This prevents unreliable text-based search methods from being used as primary analysis tools.

Code investigation requires building an AST dependency graph first to ensure safe and comprehensive analysis. This constitutional enforcement prevents premature modifications by validating all dependencies and callers, ensuring adherence to default analysis modes and preventing incomplete impact assessments.

Fail-closed behavior in AST code analysis gatekeeping blocks all work if the dependency graph cannot be built. This prevents analysis based on incomplete or unreliable data, ensuring that no code investigation, impact analysis, or refactoring proceeds without a validated AST graph.

To stop unreliable text-based search from being used for code impact analysis, implement a mandatory AST graph gate. This enforces default analysis modes by requiring a detailed, validated dependency graph to be documented before any code investigation or modification begins.

You need an AST dependency graph for code modification whenever performing refactoring, impact analysis, or investigation. Mandating this graph first ensures you understand all dependencies and callers, which makes the modification safe and comprehensive.

No, you cannot use text-based search as a primary analysis tool if the AST graph fails to build. The fail-closed behavior blocks all work when the dependency graph cannot be built, preventing any analysis based on incomplete data.