arch-detectorlisted

# Architecture Detector ## Overview Profiles a codebase to identify which architectural patterns are in use, documents structural evidence for each, detects canonical combinations, and infers the compound structural rules that apply. Hostile — every pattern claim must be backed by concrete structural evidence. ## When to Use - Before running `arch-auditor` to provide it with a profile - When you need to understand the intended architecture of an unfamiliar codebase - When `docs/audit/arch-profile.md` is missing or stale **When NOT to use:** If `docs/audit/arch-profile.md` already exists and you only want to find violations, run `arch-auditor` directly — it detects inline when no profile is present. ## Individual Patterns Detected | Pattern | Key signals | |---------|-------------| | DDD | `domain/`, `bounded-contexts/`, `*Entity`, `*ValueObject`, `*Aggregate`, `*Repository`, `*DomainService`, `*DomainEvent` | | Hexagonal / Ports & Adapters | `ports/`, `adapters/`, `*Port`, `*Adapter`, driving/driven separation | | Clean Architecture | `entities/`, `use-cases/`, `interface-adapters/`, `frameworks/`; strict inward dependency rule | | Onion Architecture | Concentric naming: `core/`, `domain/`, `application/`, `infrastructure/`; no outward dependencies from inner rings | | Layered / N-Tier | `presentation/`, `business/` or `service/`, `data/` or `persistence/`; top-to-bottom dependency | | CQRS | `commands/`, `queries/`, `handlers/`, separate read/write models | | Event So