u/ArchPilotLabs

We've been noticing a recurring problem while working on larger codebases, especially with AI-assisted development.

You start with a clean architecture, but over time things drift:

• boundaries get bypassed “just this once”
• dependencies spread in ways that weren’t planned
• shared layers slowly become tightly coupled

Nothing breaks immediately, but the system becomes harder to reason about.

So we built something (ArchPilot) to experiment with this.

The idea is to make architecture something you can actually validate and enforce:

• local validation (VS Code / CLI)
• CI checks for boundaries
• visibility into drift over time across repos

Right now it supports common stacks (Node/TS, React/Next, Python, Java), but still early.

We’re trying to figure out if this is:

1. a real pain others are facing
2. something people would actually use in their workflow

For those building/maintaining SaaS systems:

• Is architecture drift something you actively deal with?
• How are you handling it today?
• Would something like this be useful, or is this overkill?

Happy to share more details if anyone’s interested.