Analysis Rule Override Scope Across Nested Project Configurations

In a code analysis platform, nested project configurations often allow teams to override inherited rule severities while sharing a common baseline. The precise boundary where an override stops applying remains unclear when projects are organized in a monorepo with multiple configuration files.

The uncertainty centers on whether an override declared in a child configuration applies only to files under that child's directory tree, or whether it also affects sibling modules that import shared libraries. Permission boundaries around who may declare overrides add another layer of complexity in multi-team repositories.

Does a project-level rule severity override in codeac apply strictly to the directory subtree of the defining configuration, or does it propagate to dependent modules outside that subtree? Is there a documented permission boundary that restricts which teams or roles may introduce overrides in shared parent configurations? If an override is scoped by directory, what is the expected behavior for generated files or vendored dependencies located inside the subtree?