ArchPilotExecutable architecture guardrails

Search docs

Docs search

Validation rule

Back to Rule Catalog
AP-DEP-003Dependency

Non-public cross-module import detected

Flags cross-module imports that do not use a public module entrypoint.

errorviolationNo auto-fix

How to fix

  1. Export the supported symbol from the target public entrypoint.
  2. Change consumers to import through that entrypoint.
  3. Keep internal-only code inside the owning module.

What the rule validates

A module imports another module through a path ArchPilot does not consider public.

Why it matters

Non-public imports couple consumers to internals and make refactors risky.

Common causes

  • Editor auto-import chose an internal file.
  • The public entrypoint does not export the needed symbol.
  • A public entrypoint declaration is stale.

Typical violation example

import from ../payments/services/internal-ledger

Typical compliant example

import from ../payments

Related rules

AP-DEP-001 - Circular module dependency detectedAP-DEP-002 - Forbidden cross-module dependency detectedAP-DEP-004 - Cross-module dependency missing from module contractAP-DEP-005 - Cross-module import bypasses public module surface

Adjacent categories

Dependency Rules

Related files/config

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

Related CLI commands

  • archpilot validate
  • archpilot validate --ci

Related docs

Rule CatalogDependency Rules & Module Contracts
AP-DEP-003 - Non-public cross-module import detected | ArchPilot Docs