layer-boundaries

To enforce layered architecture, run the `check-boundaries.sh` script to validate crate dependencies against a predefined allowlist within a brepkit workspace. This ensures proper layering and catches issues early in the CI pipeline before merging code.

A strict layered DAG for dependency management defines a directional architecture where crates can only depend on specific allowed lower layers. This structure prevents transitive dependency violations and maintains a clean project boundary in Solid Modeling systems.

Managing EdgeCurve and FaceSurface variants requires following specific dependency guidelines to maintain crate boundaries. The boundary checker validates these dependencies against the layered DAG rules to ensure structural integrity across the workspace.

Yes, dependency validation checks can be integrated directly into the CI pipeline. By running the boundary check script, the system catches incorrect or transitive dependencies early, preventing architectural violations from being merged into the main codebase.

Yes, the boundary checking mechanism is designed for Solid Modeling projects built using Rust and WebAssembly. It specifically targets crate dependency management within this technology stack to enforce strict layering rules.

A dependency allowlist is needed to prevent transitive dependencies from bypassing architectural rules. By explicitly defining allowed dependencies, the system ensures all crates adhere to the strict layered DAG and prevents structural violations.