anti-spaghetti

To detect parallel-infrastructure duplications in a large monorepo, run a structural audit scan that locates framework boundary duplications where canonical sister patterns are missing. The scan outputs a prioritized findings report detailing structural anti-patterns for architecture reviews.

Architectural anti-patterns occur when parallel infrastructure is introduced despite canonical sister patterns existing. You scan a codebase for them by analyzing framework boundaries like registries and dispatch tables, generating a formatted findings report to guide structural remediation.

Yes, you can use this structural audit during planning gates and architecture reviews for multi-repo projects. It aligns with design-specs catalogs and anti-pattern registries to identify missing canonical patterns and prioritize structural health improvements.

Yes, auditing codebase architecture requires access to the design-specs catalog, anti-pattern catalog, and debt ledger. These inputs enable the scanner to locate duplications at framework boundaries and output a formatted findings report to the configured REPORT_DIR.

The best way to consolidate parallel infrastructure is to run a structural audit that locates duplications where canonical patterns are missing. The resulting findings report provides prioritized remediation options to align the codebase with the design-specs catalog.

Parallel infrastructure appears when teams introduce duplicate frameworks or sidecars despite canonical sister patterns existing. A structural audit identifies these anti-patterns by scanning registries and dispatch tables, then outputs a prioritized findings report for consolidation planning.