hexagonal-architecture-analysis

A hexagonal architecture audit inventories domain, ports, adapters, application, and infrastructure layers to reveal layer tensions and architectural debt. It produces migration-ready reports identifying component misplacements that impede safe migrations.

Layer tension in a ports and adapters architecture is caused by misplacements like TemporalManager ownership, FilterContext wrapping, and hardcoded pipeline order. These architectural deviations introduce strain and violate true hexagonal boundaries.

Generate a component inventory by mapping spatial architecture elements like domain, ports, and adapters. This produces an evidence-backed artifact with explicit file references detailing data flows and constraints for migration readiness.

Yes, a data flow map is generated by analyzing hexagonal architecture components. The map traces data flows, constraints, and layer tensions across domain, application, and infrastructure layers with explicit file references like application/engine.py.

To assess migration surface in a hexagonal architecture, you need evidence-backed artifacts: a component inventory, data flow map, tension report, and migration surface report. These identify architectural debt and explicitly guide refactors.

You should avoid a hexagonal architecture audit when your project lacks explicit ports and adapters layers or when complex layer tensions like hardcoded pipeline order are absent, meaning migration-ready debt analysis is unnecessary.