ArchPilotExecutable architecture guardrails

Search docs

Docs search

Validation rule

Back to Rule Catalog
AP-ARCH-006Architecture

Module contract file exists

Checks that every registered module contract file resolves.

errorsetup-gapNo auto-fix

How to fix

  1. Create or restore the contract file.
  2. Update the registry contract path.
  3. Keep contract files versioned with module changes.

What the rule validates

A module registry entry references a contract file ArchPilot cannot read.

Why it matters

Contracts define dependencies and public surfaces for module boundary validation.

Common causes

  • The contract file was not created.
  • The contract path is wrong.
  • A module was moved without moving its contract.

Typical violation example

A module exists but its .archpilot contract path points to a deleted file.

Typical compliant example

Each registered module has a readable contract file.

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 CatalogDependency Rules & Module Contracts
AP-ARCH-006 - Module contract file exists | ArchPilot Docs