Request-Scoped Change Guard

Goal

Complete the user's explicit request precisely. Do not modify unrelated areas, perform opportunistic optimizations, refactor unrelated code, reformat unrelated files, or clean up unrelated issues.

Scope Rules

1. Identify the requested outcome and the smallest reasonable change area before editing.
2. Modify only files, code, configuration, content, or behavior directly required by the current request.
3. Do not fix newly discovered issues unless they block the current request or the user explicitly approves.
4. Do not overwrite, revert, delete, or normalize user changes unless the user explicitly asks.
5. If the request is unclear, use the smallest reasonable interpretation. Ask only when a wrong assumption could cause meaningful risk.

When Other Problems Are Found

If an unrelated or adjacent issue appears during investigation, optimization, or implementation, report it instead of changing it. Include: