# Change Impact Review Policy Plan

## Background

Clinic changes are frequently implemented by rotating on-call engineers with
AI assistance. A narrow requested fix can unintentionally affect adjacent
authorization, routing, compatibility, deployment, or data behavior; the
opposite risk is an AI expanding the change beyond the requested scope.

## Goal

Make an explicit change-impact review a required part of the local development
and pull-request handoff process, with evidence rather than an unsupported
claim that a change is safe.

## Implementation

1. Add an `AGENTS.md` policy requiring engineers to review the final diff and
   relevant callers, routes, configuration, and deployment consumers before a
   commit or PR handoff.
2. Require the handoff to state expected impacts, intentional non-goals, and
   any possible follow-up regression checks.
3. Require a clear no-unintended-impact statement only when it is backed by
   the review and validation actually performed.

## Exclusions

- No runtime, API, configuration, deployment, or generated artifact change.
- No modification to the Clinic module/deployment overview, because ownership
  and deployment mappings are unchanged.