ArchPilotExecutable architecture guardrails

Search docs

Docs search

Validation rule

Back to Rule Catalog
AP-ARCH-005Architecture

Module registry path exists

Checks that registered module paths exist as directories.

errorsetup-gapNo auto-fix

How to fix

  1. Restore the missing module directory or remove the stale registry entry.
  2. Update paths after module moves.
  3. Run validation to confirm every registered module resolves.

What the rule validates

A module listed in the architecture registry points to a path that does not exist.

Why it matters

Missing paths make module dependency validation unreliable.

Common causes

  • A module was renamed or deleted.
  • The registry was edited by hand.
  • Smart Init output was not reviewed after a restructure.

Typical violation example

The registry lists snapshots, but apps/api/src/modules/snapshots is missing.

Typical compliant example

Every module registry entry points to an existing module directory.

Related rules

AP-ARCH-001 - Modular monolith folder structure existsAP-ARCH-002 - Implementation profile not fully supportedAP-ARCH-003 - Architecture overview artifact existsAP-ARCH-004 - Module baseline files exist

Adjacent categories

Architecture Rules

Related files/config

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

Related CLI commands

  • archpilot validate
  • archpilot validate --ci

Related docs

Rule CatalogSmart InitDependency Rules & Module Contracts
AP-ARCH-005 - Module registry path exists | ArchPilot Docs