Concrete governance mechanics for Angular and Nx.
Keep domain ownership explicit and enforceable.
Dependency direction
Feature -> data-access -> util. No reverse coupling.
Public APIs only
No cross-domain imports into internals.
Violation triage
Block new violations, burn down legacy deliberately.
Governance in everyday engineering flow.
Core checks
- Boundary rule checks in CI.
- Cross-domain touch count in PR review.
- Circular dependency detection and triage.
Decision logging
- Capture why a boundary decision was made.
- Link decisions to impacted domains and PRs.
- Review decision drift on a weekly cadence.
AI supports governance workflows.
Practical AI support
- Drift detection from dependency and PR patterns.
- Boundary-violation triage proposals.
- Ownership suggestions from change history.
- PR scope and blast-radius analysis.
- Decision-log summarization drafts.
Guardrails
- No credentials or customer data in prompts.
- No autopilot merges for structural changes.
- Boundary definitions remain human decisions.
