Module contract file exists

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 it means

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.

Example bad pattern

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

Example good pattern

Each registered module has a readable contract file.

Related files/config

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

Related CLI commands

• archpilot validate
• archpilot validate --ci