Program change is one of the four IT general control areas the SEC names (Release 33-8810), and auditors rely on it before they can rely on automated controls. PCAOB inspectors have repeatedly found that audit teams did not evaluate whether changes to accounting systems were tested before production, or test the completeness of the population of changes (PCAOB, 2024).
AI workflows make this harder. A workflow that posts vendor bills or a toolset that lets an agent update records is a program change in every sense, but it can be edited in minutes, often by the same person who will run it. ISACA says agent logic should be treated as code, under version control (ISACA, 2025).
What the auditor will ask
- Is the workflow running in production the version that was tested?
- Who can change production, and is that someone other than the developer?
- Can you give me the complete list of changes in the period?
- Are development and production credentials separate?
What engini gives your change process
Inside a workspace, engini keeps separate development, staging and production environments. API keys are tied to one workspace and one environment, so a development key cannot touch production. Workflows can be exported and imported, so the definition you tested in staging is the one you promote, and the export can live in your own repository as the change record. Roles, including custom roles, decide who can edit where, and the audit log records activity.
engini does not run your change tickets or hold a workflow for sign-off; it has no approval step. Keep the ticket, the test evidence and the approval in your ITSM, and use engini’s boundaries to make the promotion clean. Prompts inside a third-party chat client and model versions change outside engini, so manage them in your agent platform.
