An architectural rule known only to a team can be missed by a coding agent—or a new teammate. Lint-as-architecture turns that implicit knowledge into executable checks that fail the build when prohibited structures or dependencies appear. section 10.5.1
Turn recurring violations into guardrails:
- Fix the immediate problem in the pull request. section 10.5.1
- Codify the architectural rule behind the correction. section 10.5.1
- Add a lint rule or architectural check to prevent the violation from recurring. section 10.5.1
A database boundary
If API-layer code calls the database directly, correct the call in review. When the violation recurs, add a check that fails the build on the prohibited dependency. The rule preserves a convention that previously depended on onboarding and review feedback. section 10.5.1
Checks can reduce repeated convention reviews, but they do not settle every merge decision. Policy-based triage accounts for context such as module criticality, ownership, and downstream consumers; human judgment remains necessary for architecture and tradeoffs. section 10.5.2 section 10.9
