architecture-check

To check architecture layer boundaries, run a boundary scan during code review to confirm Core, Services, and UI layers stay properly separated. This prevents upward imports and enforces strict layer ordering before merging cross-layer changes.

Detect code duplication and circular imports by running an import and duplication scan on Python modules. This flags repeated hooks, routes, and service logic while identifying broken or upward imports across app layers during refactoring.

Yes, you can enforce strict layer ordering and prevent I/O in math layers during pull request review. Boundary validation confirms Core, IS 456 Code, Services, and UI layers stay properly separated when verifying repository architecture rules.

Validate repository architecture rules after a refactor by running boundary, import, and duplication scans. This confirms the repository still follows intended layer ordering rules and catches duplicated logic before merging cross-layer changes.

Python module import validation fails with upward imports because strict layer ordering rules are enforced. Import checking detects circular, broken, or upward imports across app layers to prevent architecture violations from destabilizing the codebase.