Scope
Unbx is strongest when a rule is repeated, structural, and narrow enough that a team can predict why it fired.
Typical examples include dependency boundaries, prohibited imports, and layer-specific responsibilities.
Non-goals
Unbx does not try to infer runtime intent from ambiguous code or replace engineering judgment with opaque scoring.
If a rule cannot be detected reliably, it should remain guidance rather than pretend to be enforcement.