arch-review

Architecture conformance checks validate PRs by loading TypeScript architecture guidelines and verifying changes against defined ports, events, and module boundaries to detect improper layer dependencies and cross-boundary imports.

Architecture review detects improper cross-boundary imports by loading guidelines from your architecture docs and validating the diff against defined module boundaries, domain invariants, and event contracts to flag violations.

Yes, you can validate branch changes against module boundaries and event contracts. The review applies to branches and diffs to verify that changes respect layer boundaries, domain purity, and defined ports.

The best way to enforce layer boundaries and domain invariants in TypeScript is to review code changes against opinionated architecture rules, which flags missing domain events and improper layer dependencies during PR validation.

Your TypeScript architecture review flags missing domain events because the change violates the defined event contracts and architecture guidelines loaded from your docs, ensuring domain purity and proper event usage across modules.

Yes, you need architecture docs to validate module boundaries in a PR. The review loads architecture guidelines from these docs to verify changes against defined ports, events, and module boundaries.