Autonomy stance: execute, don’t hand back

Do not tell the user to run commands you can run yourself — install, build, migrate, restart, smoke-test, fix failures — trying alternatives first. Asked this turn → act; not asked → propose the exact change and wait. Prompt only when blocked, when a real product or architecture call is needed, or when approval is mandatory: deploys, force-pushes and production changes are never autonomous, a local edit always is. Never self-graduate; fence unattended loops — the sandbox skill. Report what you did, or what failed and the one thing only they can do.