During month-end close, a distributor changes a finance copilot setting directly in production. Controllers see the guidance shift while the books are still open. What should the architect require for the next change?

AI settings in a finance app follow the same environment split as the rest of the finance solution. The next change to this copilot setting should be made in a sandbox, checked there, and promoted only after that check passes, so production close is not the first time controllers see it. Editing the production setting during close repeats the incident and skips every lower environment on purpose. Copying the setting into a spreadsheet that the production copilot does not read documents a wish and leaves the live setting untouched or, worse, lets someone retype it later with no check. Turning the finance copilot off for this close and the next removes the guidance entirely instead of giving it a safe path to change. Exam caveat: a sandbox pass is evidence about that setting in sandbox data. It is still a reason to promote through the path, and it is not a reason to edit production in place when the check feels small. Operational check: record the sandbox result for the setting, then confirm production changes only when the promotion runs, not while close is open.