Search docs
Docs searchValidation rules
Rule Catalog
Look up ArchPilot validation rules by ID, category, severity, and fix path.
Start with the rule ID from a local validation report, CI output, VS Code finding, or Cloud finding. Each rule page explains what the finding means and the safest next fix to try.
Architecture
11 rulesAP-ARCH-001errorChecks that the configured module root exists and contains the expected module directories.
AP-ARCH-002infoReports when ArchPilot falls back from a specific implementation profile to default validation behavior.
AP-ARCH-003errorChecks that the architecture overview document exists.
AP-ARCH-004warningChecks that expected module baseline artifacts are present.
AP-ARCH-005errorChecks that registered module paths exist as directories.
AP-ARCH-006errorChecks that every registered module contract file resolves.
AP-ARCH-007errorChecks that module contract identity and field shape align with the registry.
AP-ARCH-008errorChecks that registered module public entrypoints match the public surfaces declared in module contracts.
AP-ARCH-009errorChecks that the project rule configuration file can be parsed and used.
AP-ARCH-010errorChecks that the ArchPilot project configuration is valid JSON.
AP-ARCH-011errorChecks that project identity fields are present and usable.
Dependency
10 rulesAP-DEP-001errorFlags direct circular dependencies between modules.
AP-DEP-002errorFlags dependencies blocked by dependency rule configuration.
AP-DEP-003errorFlags cross-module imports that do not use a public module entrypoint.
AP-DEP-004errorFlags an actual cross-module import that is not declared in the source module contract.
AP-DEP-005errorFlags imports that reach into another module's internals instead of its public entrypoint.
AP-DEP-006warningFlags a module contract dependency that no longer appears in implementation imports.
AP-DEP-007warningFlags modules with no declared or actual inbound/outbound module dependencies.
AP-DEP-008errorFlags dependency cycles that emerge through multiple module hops.
AP-DEP-009warningFlags modules with a high number of inbound dependencies.
AP-DEP-010errorFlags dependencies that point against the configured architecture layer direction.
API
2 rulesDatabase
2 rulesDocumentation
11 rulesAP-ADR-001warningChecks that the configured ADR directory exists.
AP-ADR-002warningChecks that ADR files include a top-level title.
AP-ADR-003warningChecks that ADR files include a recognized decision status.
AP-ADR-004warningChecks that key architecture topics have ADR coverage.
AP-DOC-001warningChecks that different-schema tenant modeling decisions are captured in an ADR.
AP-DOC-002warningChecks that architecture overview documentation mentions RBAC or role-based access control where expected.
AP-SUP-001warningChecks that suppression entries include a reason.
AP-SUP-002warningFlags suppression entries whose expiry date has passed.
AP-SUP-003infoReports suppression entries that no longer match an active finding.
AP-SUP-004warningFlags duplicate suppression entries.
AP-SUP-005warningChecks that suppression expiry dates use a valid format.
Safety Controls
3 rulesAP-SAFE-001warningFlags risky architecture changes that lack ADR evidence.
AP-SAFE-002warningFlags risky changes without rollback plan evidence.
AP-SAFE-003warningFlags risky changes without staged rollout or feature-flag evidence.
Data & Query Risk
4 rulesAP-DQR-001warningFlags query paths where multi-tenant SQL lacks clear tenant-filter evidence.
AP-DQR-002warningFlags broad SELECT * usage in paths where explicit projection is safer.
AP-DQR-003warningFlags list/query paths without obvious limit or pagination controls.
AP-DQR-004warningFlags database access that reaches into another module's owned data boundary directly.