architecture-review

Circular dependency detection in Rust is performed by analyzing `use` statements to map module relationships and generating a custom graph to visualize and report cyclic imports between modules.

Enforcing a strict layer dependency hierarchy during code review involves validating the unidirectional dependency rule, ensuring Layer N only depends on Layer M where M is less than N.

Validating module boundaries to prevent improper type leakage requires checking for cross-module dependencies and ensuring types do not unintentionally cross established architectural boundaries.

SDKs should remain thin wrappers because complex logic must reside in the core engine, ensuring architectural integrity and preventing code duplication or dependency violations across layers.

You should run an architecture audit after adding a new feature that touches multiple layers to confirm no unintended dependencies were introduced and that the architectural hierarchy remains sound.

Yes, the architecture review tool works without external dependencies, utilizing internal scripts and references to analyze Rust `use` statements and generate architectural graphs.