Isolated module detected

How to fix

1. Decide whether the isolation is intentional.
2. Connect the module through legitimate dependencies or document the intentional isolation.
3. Remove stale modules that are no longer part of the architecture.

What it means

A registered module is isolated from the module graph.

Why it matters

An isolated module may be intentional, but it can also mean stale architecture metadata or unused code.

Common causes

• The module is intentionally standalone.
• The module is registered before it is used.
• The module is obsolete and should be removed.

Example bad pattern

A registered health module has no inbound or outbound dependencies and no ADR explaining the isolation.

Example good pattern

The module is either connected through valid dependencies or documented as intentionally isolated.

Related files/config

• .archpilot/architecture.json
• .archpilot/contracts/*.json

Related CLI commands

• archpilot fix AP-DEP-007
• archpilot validate
• archpilot validate --ci