Not yet reviewed. Artifacts stay locked until you approve them.
Step 3 of 9
Technical defaults
The commands that prove work is done, and the platforms you target.
Naming your own gates stops an agent inventing plausible ones. A wrong test command reads as a passing build.
One per line, or comma-separated. These are the commands an agent must run — and show output from — before claiming work is done.
Where this rider is meant to run. Naming them stops an agent assuming a runtime you do not use.
Actions the agent must stop and ask about. An instruction file cannot enforce these — the host does — but stating them makes a violation obvious.
Ask before anything reaches production.
Ask before DROP, TRUNCATE, or any destructive migration.
Ask before force-push, history rewrite, or deleting a shared branch.
Ask before changing payment, auth-provider, or dependency major versions.
Read secrets from the environment only — never print, log, or commit one.
Ask before sending mail, posting to a third-party API, or changing DNS.