mbtorch-architecture

To enforce layering rules, validate allowed and forbidden dependency directions between core, nn, optim, and io directories to prevent architectural regressions. This maintains testability and structural constraints during code reviews and module additions.

The correct workflow for adding an optimizer or IO importer involves identifying the correct directory, validating allowed imports, prescribing test-first development tests, and proposing backwards-compatible migration notes to ensure maintainable, architecture-compliant changes.

To refactor inverted dependencies and migrate public API changes in a neural network library, apply suggested alternative designs and migration advice to ensure backwards compatibility while correcting forbidden dependency directions between core modules.

Yes, a WASM-first architecture constrains module structure by requiring changes to maintain testability and specific layering rules. You must ensure core, nn, optim, and io directories respect allowed dependency directions to preserve WASM compatibility.

Before modifying core directories to prevent architectural regressions, check module paths, search for existing implementations, follow a test-first workflow, and verify allowed imports to strictly enforce repository layout and design guidelines.