Architecture patterns / Architecture Drift
Draft
Layer-violation exemplar pending — Next.js drift narrative not yet published as pattern proof.
What is architecture drift?
Architecture drift is the gradual divergence between intended module boundaries and the actual dependency graph — layers that leak, duplicates that compete, or utilities that absorb domain logic.
Trust path: Homepage → Validation → Repository proof → Architecture Drift → Install
Why it matters
Drift compounds silently until a refactor is expensive or a cycle blocks progress. Drift plus high fan-in is a common path to production incidents after “small” merges.
What it looks like in codebases
- Domain types importing utilities that import server-only code.
- Duplicate authorities for the same concept in parallel folders.
- Layer violations flagged in structural scans.
Real repository example
No indexed exemplar yet. See Next.js repository proof for the current flagship analysis while this pattern page is in draft.
How ArcSight detects it
- Layer violation reports in arc scan output.
- Duplicate or competing modules surfaced in explain narratives.
- Rising fan-in on utility folders as features shortcut local boundaries.
$ arc scan# Layer and boundary inventory
What to inspect first
- Documented layer violations involving your change surface.
- Modules that gained fan-in in the last release without an explicit design review.
- Parallel type definitions with overlapping names or shapes.
What to do next
- Fix the smallest layer violation that closes a refactor path.
- Consolidate duplicate authorities before adding features on drifted paths.
- Re-scan after boundary fixes; drift repair is incremental, not one-shot.
Run ArcSight on your codebase
Install locally, run arc impact on the module you plan to change, and get structured evidence — before you merge.
npm install -g arcsightInstall →