Approve a change
Approvals keep high-risk actions human-owned. Aegis can prepare work, evidence, and recommendations, but approval decisions should come from a human operator.
When Approvals Appear
Approvals can appear for:
- repo writes;
- external writes;
- connector actions with side effects;
- profile or routing changes;
- workflow authority changes;
- high-risk policy classes.
Review The Approval
- Open the run or approval queue.
- Read the approval action type and policy class.
- Review the reason and risk summary.
- Open linked artifacts.
- For repo writes, inspect the patch bundle and changed files.
- Check verifier output.
- Check hashes when they are provided.
- Add a reviewer note when useful.
- Approve or reject.
Repo Write Checklist
Before approving a repo write, confirm:
- the changed files are expected;
- the diff matches the requested work;
- no unrelated files changed;
- tests or verifier commands passed;
- the approval applies to the exact patch bundle;
- the policy class is correct.
Rejecting Work
Reject when the diff is wrong, evidence is missing, tests failed, scope expanded unexpectedly, or the action is not worth the risk.
Rejection preserves audit history. Depending on the run, you can add guidance and retry, ask for a smaller change, or cancel the run.