Missing feature-flag or staged rollout evidence for risky architecture change

How to fix

1. Add rollout evidence to the ADR or runbook.
2. Introduce a feature flag or staged deployment plan when appropriate.
3. Document monitoring and completion criteria.

What it means

A risky architecture change lacks evidence that it can be rolled out gradually.

Why it matters

Feature flags and staged rollouts make architecture changes observable and reversible during adoption.

Common causes

• The rollout plan is only in a ticket.
• The code path changed globally at once.
• Feature flag names are not linked from architecture docs.

Example bad pattern

All traffic moves to a new routing path with no staged rollout evidence.

Example good pattern

The change is gated by a named flag and the ADR lists stages and success checks.

Related files/config

• docs/adrs
• docs/runbooks
• apps/api/src

Related CLI commands

• archpilot validate
• archpilot validate --ci