brownfield-drift

To detect architecture drift in a pull request, run a drift check against a base commit. This compares repository changes against machine-readable PLAN.md constraints to report only newly introduced boundary violations like forbidden imports or circular dependencies.

Architecture drift detection identifies when code changes violate module or service boundaries defined in PLAN.md. It enforces constraints by flagging forbidden imports, direct inter-service imports, and ownership rule breaks during code reviews or scheduled health checks.

You can run drift analysis for a single specified rule to speed up reviews and remediation. This focuses the boundary violation detection on a specific constraint from your PLAN.md file, reporting only the violating edges for that rule.

No, this drift detection requires a machine-readable PLAN.md file in the repository. It compares repository changes against the architecture boundaries and ownership rules defined within that PLAN.md file to identify violations.

The best way to report only newly introduced violations is to run the drift command with a base commit parameter. This restricts boundary violation reporting to new violations introduced since that base commit, providing guided remediation aligned to PLAN.md intent.

Yes, you can apply drift detection during scheduled architecture health checks. It identifies cross-module or cross-service changes that may have introduced drift, reporting specific violating edges and suggesting fixes aligned to your PLAN.md constraints.