Check dependency-direction discipline (routers depend on services, services depend on models, not the reverse) within the EXISTING FastAPI layered structure — not a prompt to migrate to formal Clean Architecture with ports/adapters/use-case layers. Use only when the user asks specifically whether a dependency points the wrong way, or when reviewing a new module's imports for layering violations. Explicitly does not propose introducing new architectural layers; this project's layered router/service/model pattern is the accepted architecture and any request to formally adopt Clean Architecture (Uncle Bob style) should be redirected to a scope discussion, not executed.
