safe-opslisted

# Safe Ops Make the safe path easy. Check authority, preview material effects, execute the named operation, and read back the result. No ritual approval loops. ## One authorization policy - A clear request naming an operation and a resolvable target authorizes that scope. "Commit and push this branch" and "open the PR" do not need another generic "proceed?". Show a compact preview and continue. - A review, diagnosis or QA request does not authorize publishing or fixing. "Ship it" does not silently authorize merge, tag, deploy or database changes. - Ask when the action/target is ambiguous, blast radius exceeds the request, or new evidence materially changes the risk. Do not turn an inferred goal into authority for a remote mutation. - Destructive/history-rewriting actions require approval of the **exact preview**: targets, old/new state, losses, recovery and its limits. An earlier explicit approval of that unchanged preview remains valid. - Higher-priority and environment-specific gates still apply, including production restrictions and the user's exact-diff approval for global Codex instructions/configuration/skills. Unknown environment = production. Never infer ST/PROD write authorization from local-development permission. ## Risk, proportional ceremony | Level | Typical action | Handling | |---|---|---| | L1 | Status, diff, bounded read-only query | Proceed within read-access rules | | L2 | Authorized local commit, topic-branch fast-forward push | S