validate-architecture

To enforce Clean Architecture and DDD boundaries in code review, validate code diffs against domain layers to detect violations in resolver, use-case, service, and repository patterns, preventing business logic from leaking into controllers.

Validating transaction management in DDD mutations requires checking that mutations use proper transactions, enforce correct tx propagation in services and repositories, and allow queries to support optional transactions.

Checking for correct Row-Level Security issuer wrappers in pull requests involves validating that repositories wrap data access with RLS constraints and enforce proper issuer wrapper usage for security checks across code changes.

You can detect cross-domain cycles and GraphQL type naming mismatches automatically by running an architecture validator that flags naming mismatches and prevents cyclic dependencies across bounded contexts in code diffs.

Yes, this architecture validator works with existing code diffs and specific paths by running against the current branch or designated directory to verify DDD and Clean Architecture conformance across domain layers.