Architecture and layer boundaries

When to use: Layering and boundaries, web vs public API, app layout (clients, routes, logging), ports/adapters, runtime-portable domain/shared/utils code, multi-tenancy, DDD layout, or anti-patterns.

App boundaries (apps/*)

Apps only handle:

• Input validation
• Authentication and authorization
• Organization access enforcement
• Routing to domain use-cases

No business logic in handlers, controllers, or jobs.

Application layout (apps/*)