anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Require approval before ATVM command execution

Browse Source 
Update the ATVM automation guidance so exact planned commands must always be shown for operator review before any execution. Require explicit approval before running cmc-templates.py, run-sorry-cypress.py, or any other ATVM run command, and require fresh approval whenever the displayed command set changes. Also record the new approval rule in the ATVM run-learning notes and operator instruction file.
This commit is contained in:
anthony.wen
2026-03-20 18:58:29 -04:00
parent c18b42549c
commit eb2ab44e86
3 changed files with 35 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
atvm/AGENTS.md
View File

@@ -89,12 +89,14 @@ Do not treat example options, excludes, plugins, or filters as default operator
1. Before planning a new run, check for active automation processes.
2. Report running/not-running status.
3. If running, ask before termination; terminate only with explicit approval.
4. Always show exact planned command(s) before execution.
5. Execute only after explicit approval.
6. If monitoring is not requested, report immediate command success/failure and any errors.
7. Monitor completion only when explicitly requested by the operator.
8. For monitored runs, allow long runtime windows (15-30+ minutes or longer) and continue until completion unless operator instructs otherwise.
9. Do not terminate monitored runs unless the operator explicitly instructs termination.
4. Always show exact planned command(s) exactly as they will be executed before execution.
5. Never execute `cmc-templates.py`, `run-sorry-cypress.py`, or any other ATVM run command until the operator explicitly approves the displayed command(s).
6. Approval is required for template-generation commands as well as the runner command.
7. If the operator changes the requested scope, plugin, config, build name, or any other option after commands are shown, rebuild the commands, display them again, and wait for fresh approval.
8. If monitoring is not requested, report immediate command success/failure and any errors.
9. Monitor completion only when explicitly requested by the operator.
10. For monitored runs, allow long runtime windows (15-30+ minutes or longer) and continue until completion unless operator instructs otherwise.
11. Do not terminate monitored runs unless the operator explicitly instructs termination.
### Status Request Format
When the operator asks for run status, report in this order: