Required ADR missing for architecture context

How to fix

1. Add or update an ADR for the missing context.
2. Use clear keywords for the architecture topic.
3. Link the ADR from overview docs when it explains a central system decision.

What the rule validates

ArchPilot expected an ADR for a configured or detected architecture context but did not find matching evidence.

Why it matters

Core choices such as tenant model, API style, and dependency boundaries should not live only in code.

Common causes

• A major architecture decision lacks an ADR.
• The ADR exists but uses different keywords.
• The required ADR context changed after configuration was written.

Typical violation example

The repository config says REST, but no API style ADR exists.

Typical compliant example

An accepted REST API style ADR explains the decision and consequences.

Related rules

Adjacent categories

Related files/config

• docs/adrs
• docs/architecture/overview.md

Related CLI commands

• archpilot validate
• archpilot validate --ci