change-impact

name	change-impact
description	Trace a repository change from modified inputs through affected behavior, callers, consumers, configuration, persistence, and operational surfaces. Use when planning verification for a diff, assessing regression risk, or selecting checks and probes that cover the changed behavior.

Change Impact

1. Start from the changed paths and focused diffs. Separate committed facts from hypotheses.
2. Identify changed contracts: inputs, outputs, errors, state transitions, persistence, commands, and user-visible behavior.
3. Trace direct callers and consumers using repository evidence. Continue only while each edge has a concrete source reference.
4. Include configuration, CI, packaging, documentation, migrations, and runtime boundaries when the change can reach them.
5. Rank impact by severity and likelihood. Prefer existing checks that observe the contract from a consumer boundary.
6. Propose a generated probe only for a named hypothesis that existing checks cannot cover.

Required evidence

For every proposed verification step, provide:

• the affected behavior or invariant;
• the source paths establishing the impact path;
• the exact existing check, command, or bounded probe;
• the observable result that would confirm or falsify the hypothesis;
• a stop condition preventing unrelated exploration.

Do not claim impact from naming similarity alone. Mark an unverified edge as a hypothesis.