inspect-role-naming — Architectural Role & Nomenclature Auditor

Domain Rubric

1. Scope & Tolerability Guardrails (What to Ignore)

• Confine to Load-Bearing Risks: Focus exclusively on dangerous architectural misrepresentations, runtime collisions, or boundary schema leaks.
• Tolerate Benign Code: Tolerate minor local helpers (< 3 methods), internal variable brevity, benign metrics/logging in accessors, and cosmetic style differences; never force refactoring on working, cohesive code.
• Governing Reference: Evaluate naming and role alignment strictly against references/role-naming-rubric.md (or the host repository's authoritative naming specifications, which always take precedence).

2. Decision Bifurcation: [RENAME] vs. [REFACTOR]

• [RENAME] (Pure Nomenclature Drift): The underlying responsibility is singular and sound; only the identifier/suffix drifted from references/role-naming-rubric.md. Fix is localized and low-risk.
• [REFACTOR] (Role Dishonesty / Responsibility Leak): The symbol name conceals multiple disparate responsibilities or makes false promises (e.g., repository calling external APIs). Structural extraction must occur before renaming.

Canonical Output Contract

# Role & Naming Audit Dossier: <Target Scope>