naming

To fix module naming drift, you identify where the current name no longer matches the module's behavior, then propose a strict, honest name that gates scope and enforces single-responsibility boundaries across your codebase.

The best way to enforce single-responsibility naming is to apply governance rules like one-module-per-thing and prefixed or suffixed naming conventions across Rust crates and TS packages to prevent scope leakage.

You need to flatten or extract a new module during a refactor when scope drift occurs and the existing module name can no longer honestly describe its expanded responsibilities, signaling a boundary violation.

Yes, strict naming discipline applies across directories and test corpora to tie structure to a clear, singular name, ensuring code organization remains honest and preventing scope creep through consistent governance signals.

You apply route-group discipline and short-name conventions by enforcing governance signals that tie directory and module structures to singular names, ensuring your architecture maintains clear boundary definitions and prevents scope leakage.