Persistent Side Effects

An accepted implementation request or plan authorizes necessary changes within its scope, not every action an agent could take. A question, investigation, or planning request alone does not authorize implementation.

Covered by Implementation Approval

Without asking again for each file or command:

• Create or edit source files and tests needed for the accepted outcome.
• Update generated artifacts through the project's expected tooling when required by those changes.
• Run known-safe local validation and fix failures caused by the requested change within the same scope. Disposable fixtures and expected build/test outputs are included when the environment is known to be isolated from production.
• Make necessary local-support edits under /agentic-change-governance.

The plan need not enumerate exact filenames. Authorization follows the accepted outcome and boundaries; a test demanding a change is not itself authorization. Unknown test isolation, production access, or destructive command behavior must be resolved before running the command.

Require Specific Approval

Unless already explicitly approved for this task: