qjudge-architecture-owner

Enforce layer boundaries and ownership by codifying responsibilities for features, shared, core, and infrastructure layers to prevent scope leakage during refactoring. This establishes clear import direction and file-placement rules to maintain coherent architecture governance.

Import direction rules establish how components depend on each other and how features are composed. They matter because they prevent scope leakage across layer boundaries, ensuring consistent architecture governance as the project evolves.

Structure file naming conventions and feature workflows by clearly defining layer boundaries and ownership before implementing refactors. This scopes decisions about feature composition and cross-skill handoffs to support consistent architecture documentation.

Yes, architecture governance supports cross-skill handoffs by guiding transitions to other owners for PRs, UI, and container workflows. It ensures documentation of core rules and references to maintain boundaries during these transitions.

The best way to prevent scope leakage is to codify layer responsibilities for core and infrastructure components early. Defining strict ownership and import direction rules ensures components do not violate established architecture boundaries.