What problem does it solve? Teams working on the iWana neXt platform need consistent architectural review of code changes and design proposals to prevent boundary violations, tenant data leaks, and unauthorized stack deviations before they reach production. ## Core Features & Use Cases - Boundary and Coupling Review: Detects cross-module table access, circular imports, and ad-hoc calls that break the modulith structure. - Multi-Tenancy Validation: Verifies per-request tenant resolution, schema isolation, and absence of hardcoded tenant identifiers in PostgreSQL setups. - Stack and Security Compliance: Checks proposals against the approved stack (NestJS, Next.js App Router, TypeORM, Turborepo, BullMQ, OpenAPI) and audits security, PII exposure, and audit-trail requirements. - Use Case: Before merging a pull request that adds a new billing endpoint, run this review to confirm it respects module boundaries, resolves the tenant per request, updates the OpenAPI contract, and includes an adequate testing strategy. ## Quick Start Review this proposed change to the billing module and tell me whether it respects the modulith boundaries, multi-tenant schema isolation, and the approved NestJS stack.
