Missing ADR coverage for risky architecture change

How to fix

1. Write or update an ADR.
2. Include context, decision, consequences, and rollback notes if relevant.
3. Link the ADR from the architecture overview or related docs.

What it means

ArchPilot found a change pattern that should have an architecture decision record.

Why it matters

Risky architecture changes need review context that survives beyond a pull request.

Common causes

• A boundary, tenant, API, or persistence decision changed without an ADR.
• The ADR exists but is not linked or keyword-discoverable.
• A generated report found risk before documentation caught up.

Example bad pattern

A module boundary is changed with only an inline PR comment.

Example good pattern

An accepted ADR records why the boundary changed and what teams should expect.

Related files/config

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

Related CLI commands

• archpilot validate
• archpilot validate --ci