Modular monolith folder structure exists

How to fix

1. Check the configured module root.
2. Move modules back under the configured root or update the architecture configuration.
3. Run validation again after the filesystem and configuration agree.

What it means

ArchPilot could not confirm the configured modular-monolith structure on disk.

Why it matters

Module validation depends on a stable module root. Without it, dependency and boundary checks cannot be trusted.

Common causes

• The module root path is wrong.
• Modules were moved without updating ArchPilot configuration.
• The repository is not using the expected modular-monolith layout.

Example bad pattern

"moduleRoot": "apps/api/src/modules" but modules live under src/features.

Example good pattern

"moduleRoot": "apps/api/src/modules" and each module has a matching directory under that root.

Related files/config

• .archpilot/architecture.json
• apps/api/src/modules

Related CLI commands

• archpilot validate
• archpilot validate --ci

VS Code / Inspector action

Open Smart Init or Inspector configuration review and confirm the detected module root.